Actually, that doesn't look like a u-turn node problem to me. Since you have to be able to get into and out of a dead-end road, this is a route that's theoretically available to Waze. Admittedly it doesn't look very good, but it's technically valid.
In my experience, a selfcon (u-turn node, highlighted red) would cause a slightly different problem. If there was a selfcon at Briarthorn & Midland affecting the routing, I would expect to see the Waze route turn back on itself just where the pin is in your image - without routing into & out of Midland. Maybe the selfcon you saw is a "soft-enabled" turn: Waze could
have used it, but preferred the extra short length of Midland and a "hard-enabled" right turn back out again.
I originally experienced this when I first started with Waze. On my daily route to work I reach a T-junction. Waze always wants me to go left to follow some fast highways inhabited by crazy London drivers trying to get to work! I prefer to turn right and take a quieter route. It may add a couple of minutes to my journey but it's shorter & far less stressful.
Well when I turned right, Waze would direct me to turn back on myself at the next junction. Then, when I passed that one, it would happen at the next junction and the next, before Waze would eventually "give in" and calculate a new route. When I got into the editor there was nothing visibly wrong with these junctions. But after I rebuilt all 3 by pulling the roads from the junction node then rejoining them, the problem went away. That was before this script highlighted these junctions, but that is the only manual method to remove selfcons.
Incidentally, I think this is how selfcons are created (and they are still being created). When someone gets a route like this they do their u-turn at the junction
and go back the way they came - and Waze enables the turn back onto the segment they came from because it someone doing it.