I posted before about the order that the ShowViewForRecord function searches for forms of the name you pass to it (ie: first searches legacy and then new active forms). The problem before caused a legacy view to win out over an active form in the case where they both had the same name.
I just got a confirmation that this will be changed in version 6.2. In version 6.2 the new active form will win out over a legacy view of the same name when calling ShowViewForRecord. That is great. IMO, everything should always assume new active forms. I should have to do extra things to use a legacy view.