No worries.
If you need to work around it in 2014-2016 you can, believe it or not, locate the section marker that "represents" the view and use the ElementMoveUtils (or ElementTransformUtils? can't remember) to actually move the section cut (or elevation marker). Still won't help with trying to change the cut depth in section views but you can do things like rotate the view on the page (by rotating the section marker about its view normal axis) and generally moving it around (that's how my ViewSync app does it btw)
I hear you on 4 releases but it's a huge ship they're driving over there: not so easy to turn that beast. :) I do think they pay attention to impact though so it often helps to paint a picture of the severity of a bug, e.g., how much potential revenue is at stake, number of users affected, etc. I think if you look through some of Jeremy's responses you'll see the list of information that helps them prioritize improvement of a "less than helpful feature". ;)
happy elevation moving.