I'm not sure of some details - for example, were Jumps something that wasn't even originally planned or were they something that was always planned, but wasn't expected to be ready for original shipping.
However, I found that WT did specifically mention it way back in early October 2015.
And we know there were hardware fixes that were necessary at least as late as October 2016.
Now, we have at least three different things to consider here. First, some argue that this is "scope creep". Well, if it was always intended, then I say it is not. After all, why should firmware or software people not go ahead and do stuff while hardware is being changed?
But what if this is something that they came up with after the original shipping date? Okay, could be considered scope creep - but, again, if they can do it during the time things are delayed anyway, I don't have a problem with it.
Which brings us to the third item, which fits what you are saying and I think is the best point.
That is, if this capability, whether originally planned for or not, is the only gating issue, why not just ship since it wasn't originally advertised (I'm not sure when it may have first been mentioned - I only have forum posts to go by, not old reports elsewhere on their site)?
But here, once again, we get into multiple branches. Even if original buyers purchased without this being part of the description, what of all the later buyers who did see it as part of the deal?
Most critical though is how much of these connection issues are because of the many jump possibilities and how many would exist even if just one connection was possible? If changes Apple made would mean there would still be issues to be solved, then the jump thing isn't the key issue. And people with other OS system have reported issues. I guess we could eliminate old systems not designed for blue tooth low energy, but I don't have enough info to be sure where all the problems are.
My hope is that, first, no one has greater problems than I have - which means sometimes the connections (whether first turning on or jumping) are not a quick as they used to be. Before some of these OS changes, we were looking a just a couple seconds to connect with a jump. That still happens, but on my Mac it can sometimes take longer - but only bothersome because I like how fast it used to be! I could live with it just fine as is.
If that is the case, and no other issues (that's a big if), then I would be all for shipping as is if necessary. If they think they have a notable improvement that just needs some basic testing and it will delay things a week or two, fine. If it doesn't work out, they can still go back to this version and ship.
Too bad we really don't know enough about the overall situation. Not saying WT should tell us everything, but there is no doubt but that I'd love to know more about it!