Why does this being implemented mean Eureka gets delayed again? They've already said Eureka's coming out in the mid-patch cycle "tide-over" patch. It's 99% of the way there, only a catastrophic event would cause it to be pushed back since it finally has an announced date after many push-backs.
If they were even planning for improvements to the MSQ dungeons that's all it'd be right now probably: planning, researching specifications and resource requirements, risk/reward ratios, etc. Do you even SDLC? Saying "SE can't fix a thing because a different thing will be pushed back!" is dumb. Especially when the different thing in question is already set to go live a few weeks from now. A company this large knows how to plan and schedule resources effectively.
SE can certainly start looking at a more nuanced solution to the problem. You don't have to commit to the results of the research- someone looking into the issue does not mean you suddenly have to divert ALL of your resources -even the guy who sleeps in the corner with his eyes open- to work on a resolution. For all we know they've already had a team research the problem and possible solutions and this is the best form of remediation we can expect. But if we ask for more, and make a compelling case for it, SE can slot it in for Dev time (assuming there is a prayer in hell they can finagle the spaghetti code to behave). Doesn't mean it'll ever go live. Doesn't mean we'll ever even hear about it. But asking for a better implementation of a dull story segment does not suddenly mean all the fun stuff gets pushed back indefinitely.