The entire situation is just not great. I feel like every side has been childish in the argument regarding Rust usage in the kernel.
The whole thing is worrying and somewhat sad. I think Linus should have given clearer direction of what the end goal is with letting Rust into the Linux kernel, and should have given the existing C maintainers and contributors a better idea of priority with regards to existing patches, new features or Rust extensions. It seems it is very much up to an individual to decide what they focus on.
Understandably the existing C maintainers & contributors are going to feel torn between the above priorities and if it wasn’t for the Rust evangelists they would not be having this issue. They give up a lot of their free time to do what they love, which is to build and maintain the kernel in C. There may also be a certain fear factor in that if the whole kernel goes Rust, where do they fit into that?
I feel what we are actually going to end up with is a complete mess of a code base, some of which will be C and some will be Rust. That is going to be very hard to maintain going forward.
I personally feel there should have been a separate Rust4Linux kernel project setup, where it could run in parallel and existing maintainers & contributors who wanted to take part could, and those that don’t want to take part are substituted by people who do. Eventually you would be able to swap over to an entirely based Rust kernel (if that is what the plan is?).
As a side note I was reading up on the history of Rust ( Rust (programming language) ) and had no idea this was the case -
On February 8, 2021, the formation of the Rust Foundation was announced by five founding companies: Amazon Web Services, Google, Huawei, Microsoft, and Mozilla.
Not sure, how I feel about that 
I have not been following this situation, but I agree that a Rust4Linux kernel project would be ideal and then it would not interfere with the kernel being written and developed using C, as it has been since its beginning.