Just fork the project, collaborate online over git and get rid of all the bureaucracy/bureaucrats. This used to be quite common (that's why we have so many BSD distributions).
The BSDs, for better or worse, didn’t have this problem because they mostly forked in the 90s and early 2000s. There were fewer (beneficial!) ecosystem assumptions.
And besides, this assumes that anybody really wants to do something as drastic as fork. I’m not privy to any of this, but it seems like the most “extreme” public position is nowhere close to forking Rust itself.
If they aren't coders and are "toxic" on top of that, get rid of them? Looks like a no-brainer to me.
People upvoted my clueless comment because the assumption is that any people called "core" of a FOSS project must be the coders, or else something is wrong.
If you want a hint on what's wrong, here's one for you: discourse on the Internet sucks in part because of people such as yourself making "clueless" comments.
The issue is that, there is no process to do that within the Rust-lang organisation. The core team is only accountable to themselves at this point.
I suspect there are reasons why it doesn't simply go down like that. Perhaps it's simply a lack of motivaton; or else hands being tied in various ways (invariably connected to money somehow).
Probably the best thing you can do as a FOSS developer is never grab any dollar waved in front of you and put it in your pocket, if you see so much as a tiny, barely discernible cotton fiber connecting that dollar to some people or conditions.
Yes, some of them may not have much open source Rust code out there (as they use Rust for commercial/proprietary products), and if they do it's not some "ingenious" solutions that other individual contributors in the Rust ecosystem have created, but they all code, and they all know Rust very well.