Sure, I understand that. There are different definitions of "hack", but I think a better one is "using nonstandard editing practices to accomplish something that standard editing practices cannot accomplish".
Here, maybe each way is somewhat of a "hack", considering that the former iteration of it used two parallel segments for an undivided roadway. But the other way at least looked normal, in such a way that there's no chance a passing editor would consider it some sort of mistake, and such that it didn't throw any Validator flags (not that that in particular is evidence of whether an edit is okay, but it does signal passing editors that something might be wrong, whether or not something is wrong).
There's also the fact that Waze 4.x shows the name of the current road on screen, and that can be potentially quite confusing for someone on the second half of that ramp, thinking, "Wait, I just got off SR-68!?"
My point, however, is that the amount of work that went into reconfiguring this interchange far exceeds the amount of work it would have been to maintain it in the previous configuration ("if it ain't broke, don't fix it"), especially when you have to start explaining it to every passing editor.
Simplifying the map is not an end in itself. Our goal is not to make the map "easier" to edit. We are here to make the app work the best it can with the map we have, and secondary to that is making the map understandable to other editors, not necessarily simple. In some respects, in some areas, the Waze map has been or was oversimplified for a long time, and that comes at the expense of ease of editing. Why do you think so many noobs have taken an undivided road and built them into divided roads? Because it's reality. Because it's not easy to understand why someone would draw a clearly divided roadway as a single segment. Because the editing rules that came about because of that are not as easy to fathom as they would be if the segments were simply drawn in ("why all these turn restrictions?!").
Why did we do it that way? This powerful spectre of "simplicity" that has haunted us for half a decade, making us edit the maps in ways that are more difficult to understand (against our secondary goal of making the map understandable to editors), forcing us to "reach our destinations" when we are still on the wrong side of the road (against our primary goal of making the app work well)...
Maybe this reconfiguration is marginally "simpler" (OK, two fewer nodes on the connected segments, though you still have the same number of ramps...), but it's more difficult for a passing editor to understand, and it has negative effects on navigation in the client (historical data is lost, plus confusing current road name display in 4.x). So, where does that leave it?