So to summarise my understanding of this rollout:
1) leave main game in a state riddled with bugs across almost all sections of it, many of them introduced with a recent major update (Ascension)
2) ignore questions from players about bug fixes for even just the worst offenders, and refrain from providing an update on which will be addressed and when
3) work on a new major update (Trailblazers) that may have major implications to the existing game
4) instead of getting that tested via a Beta in the original sense of the term (and obtaining valuable feedback on technical but also gameplay level), just release it to the masses with many questions still unanswered, while being aware (hopefully) of a poor track record when it comes to sensible initial balance setting
5) to up the stakes in order to not make things too boring for everyone, apply the YOLOL principle by ignoring past track record of seemingly un(der)tested updates, and release it into the wild i.e. the live client as is, while still calling it a Beta (of sorts)
6) hide again post-deployment in the Winchester, similar to post-Ascension, simply disable the most broken aspects of the update, and wait for things to blow over
I can't see any major red flags with this tried and trusted deployment approach applied throughout the industry, and I'm sure it will go swimmingly well.