change very fundamental things in the project

That's not what's happening. Right now, modules written in Rust are completely independent from modules written in C. If a Rust module wants to interact with a C module, it has to use that module's API, as it is intended. If that API changes, the Rust module has to adapt to it. Nobody is forcing C developers to change anything they don't want to. In the latest tantrum, a kernel developer called Christoph Hellwig was exposed sabotaging Rust projects: he was NACKing Rust PRs that interacted with the DRM API even though they touched none of the code he was maintaining, nor required any changes be made by a C developer. In the fallout, two Asahi/ARM developers left the mainline kernel, and one of them retired completely because of burnout.

Wrong opinions can exist if they are formed using incorrect assumptions. Hellwig had no right to sabotage the Rust projects, and certainly no right to call Rust-for-Linux developers a cancer on the LKML.

They are using a shitty language that does almost nothing for them and doesn't guarantee the final binary will do anything close to what the source implies. There's no sides to this. It's just reality.

If they aren't trying to migrate away from it, it's not good. If they actively insist on harassing the people trying to help them migrate away from it, they are the problem.

People make it sound like its some extreme time consuming task to learn rust. Rust actually gives helpful compiler errors tho and there's a lot of resources online.

I was able to start making some basic things in rust (like an ascii-rendered brute force n-body simulation) with the help of a few google searches after just like 2 days of messing around in my free time. I'm sure reading kernel stuff requires much more advanced knowledge than what I have but it's really not a large barrier.