First of all, thanks so much for taking the time to respond to my question.
I am relieved that you mention using bowties as an option for solving this since it is something that I've already attempted with some success.
Recent bowtie-style updates to an overpass near my office weren't received very well by "end-users" (even though it was invisible to the turn/voice instructions, I guess it was enough for people to notice the horizon panning back and forth when they went through the intersection to mark it as a map "problem" rather than recognize it at a map "solution").
I was going to dig up an example of where I've used bowties with success and to my horror I found something that defies the short segment theory we both believe in (I promise this wasn't meant to be a trick question):https://www.waze.com/editor/?zoom=5&lon ... TTTTTTTTFT
Unless my eyes deceive me, it looks like waze preferred sending a wazer through 3 segments instead of directly left at the node.
Here's a clean image of just the intersection showing the arrows at the node without the GPS Trace or Waze Route overlay:
As an aside, I tried to keep the angle as obtuse as possible to avoid the routing instructions to consider it a turn for wazers that didn't need to turn at the intersection. I know that I've had sharper angles than this without that problem, so I'm not sure where that came from in this case, either.
My resolution for the intersection by the office was to get rid of the dual lanes altogether for a distance far enough away from the ramps that hopefully it will always be cheaper to be routed correctly. However, this approach has also backfired on me when a mapper goes behind me and just adds all the lanes and short segments back again.