Nope, using server groups as a means of organizing server groups which are not designed to be organized is the hacky thing here.
It is merely a workaround which users came up with because TeamSpeak for the longest time failed to improve the user experience of their aging product until they realized that it’s too late and they needed to build a new user experience from scratch.
Organizing server groups in categories / folders / whatever would be the way to go here but it needs to be done in a way which won’t break backwards compatibility with older clients which don’t support it, especially since some users are complaining about recent client versions changing existing features to improve compatibility with the upcoming new client generation and those users refusing to update because of that.
I imagine remaining compatible with TeamSpeak 3 being sort of a road block for new features at times because it can potentially limit the variety of new features to those which won’t cause the protocol to change in a way that TeamSpeak 3 clients would no longer be able to understand it.
I don’t know too much about the inner workings of the software these days (and I probably don’t want to) but I think I remember protocol extensions causing compatibility issues in the past where older clients would throw protocol errors when connecting to newer servers because those servers would unexpectedly send more data than those old clients expected.
Anyhow, solving an UI usability issue by adding a new permission which isn’t even a permission is definitely a horrible idea from a software development point of view and definitely doesn’t make for a good quality software product.
I can only hope that none of you who seriously suggest dirty hacks like that are in charge of actually developing software. In some companies, that would probably get you fired.