This takes very long and is error-prone, so having a compiler that can build even an intermediate version is already a big help.
You don't have a real language until there is a stable specification and multiple independent implementations. Until then it's just an experimental toy.
And people do see the pain here as a problem, that's why the project in this very thread exists. I think most in the Rust community see mrustc and the pressure that an independent implementation brings process wise as a very good thing for the language.
It should probably be still functional, or easily fixed if not.
That doesn't mean Python isn't useful! It is in fact a wildly successful tool that has spawned a large ecosystem of packages and a diverse group of users. But it unfortunately does not qualify as a true language, for it lacks the necessary ingredients: a formal specification of the language and more than one implementation of said specification.
This has a "I will cancel my subscription" letters to the editor feel, as if anyone cares :-)
I mean, there are pros and cons to any language and ecosystem. "I found some fault in bootstrapping approach and will condemn the whole language/effort for it" is a hardly a reasonable argument...
As if regular devs often have a need to bootstrap from scratch themselves...