Single Instance End Condition Problem and Design Stages

The term “single instance end condition” probably isn’t an
official term.   So I will describe it
before asking for addition help.  A
single instance end condition problem occurs when you have a template that has
multiple end condition solutions and when applied to a corridor you have a
single instance of an end condition within a series of sections.  For example, a template could have 2 end
conditions solutions; one to draw a simple fill in-slope and another to draw a
ditch section.  The template may solve –
draw for a series of corridor cross sections. 
The first and second sections may solve as a fill slope. The third
section solve as a ditch section.  The
fourth and fifth section may solve as a fill slope.  The third section (ditch section) can be
considered a single instance end condition within a series of sections.  This section may have a valid solution but it
may not model well and or draw correctly in the cross sections.

I have worked around the single instance end condition
problem a few different ways.

1. 
   Adding a key station to create at least 2
   consecutive solutions can solve the problem. 
   In the example above the key station would be added adjacent to the
   third section.  If the key station is
   close enough to the single instance end condition the new section is usually
   the same.  After the key station is added
   you would no longer have a single instance and the problem would be solved.
2. 
   Changing the temple drop interval may also
   adjust the series to avoid a single instance. 
   However it may also create new single instance end conditions problems.
3. 
   You can eliminate the single instance end condition
   with an end condition exception.  The end
   condition exception could force an end condition that matches one of the
   adjacent sections.
4. 
   You can eliminate the single instance end
   condition by changing a parametric variable and therefore changing the series
   of solutions.
5. 
   Component name overrides can help minimize this
   problem, but some end conditions may have different numbers of points –
   different types of components.

I am looking for
better solutions than mentioned above. 
This is a cumbersome problem to begin with. Now let’s talk about
changing project settings or design stages. 
The end condition problem may re-occur at multiple design stages.  This compounds the problem and the
frustration.  New single instance end
conditions may be introduced with tighter intervals or curve densification.  It appears the harder I work to avoid single
instance end conditions the more complicated I make the model.    Does anyone have better solutions?