I think a lot of folks see a problem like this and forget that its release has never been just about BT - and certainly not just about some other company making a change.
If it was only about a change like this, I suspect shipping would have happened long ago with OTA whenever some company screwed things up.
Think of it this way. A product may have a hardware issue that must be corrected and it takes a long time to find a good enough solution. In the meantime, the company will talk about some other, non-hardware, issue that came up that was out of their control though they must respond to it. Everyone jumps on that one item, forgets about how hardware is holding back gating anyway, and says they should just ship. We saw this kind of argument back when WT was fixing hardware problems but also reported some firmware issues.
Likewise when WT adds some capability. People claim that is the problem, forgetting there were other issues already known. No reason for people not involved in solving those prior issues going ahead and putting in improvements that were originally expected to come after shipping.
But people focus on those new capabilities and assume they are the reason for the delays. And we saw this in various objections to WT not shipping.
This isn't uncommon. Human nature actually. Heck, way back in 2015, I did a couple long posts where I went back through every update WT had given and another where they described capabilities. It was an eye-opener to see it all in one place rather than scattered over months. A lot of people were surprised at what was there - including me - because I didn't remember everything from the past either.
But, in this case, maybe because I'm a treg tester, I do remember that there are other things going on. BT just seems to be a bear (though it isn't just about bluetooth) and BT low energy seems to be worse. But I think a small device like the TB, with limited battery space, probably has to go with the low energy version.
The only issue I could make about "ship now" would be based on "it's working well enough for me". I know at least one tester in the first group almost 18 months ago who said they never had an issue (they haven't posted much so I don't know if that's still true). But I think you'd find few, if any, testers who have gone through many versions who think that original was good enough.
So, we have to go to who has all the data from all the testers who are the only ones with enough information to make the decision.
Which means my only big complaint is that I wish they would communicate here more often and with more information. It won't make it ship any sooner, but I like information.