I’d say so yes. In fact I’m really surprised this didn’t happen before the release of Rack 2. I’m sure there would be plenty of volunteers from within the Rack community who would be willing to act as a first line of defence. They would expect things to perhaps be a bit buggy and would just report back with issues rather than kick up a stink. I reckon it would be good to have maybe 100 or more of them, with a good spread of Platforms, OSs and DAWs etc, who got new releases a few days before the user base at large.
One of the problems Rack faces right now is getting the blame for problems with 3rd party developers code (like the Hora example you mentioned). Users just see Rack crash, they don’t know it was a particular plugin that caused it. And when you have so many different developers submitting code to the library there should be some kind of check/process in place to prevent code that causes Rack and DAWS to crash from reaching the main user base, both to ensure a better user experience and protect VCVs reputation. Users are a lot less forgiving about this kind of thing when they have paid good money.