Yeah, but this cuts both ways. Once it is considered “supported” by CPython, users will loudly demand support in every third-party library under the sun. In a lot of cases the maintainers will have to say: “sorry, our dependencies are not available/bugfree yet”, and it just leads to lots of spilled ink and no-one being happy.
The ecosystem (by which I mean first and foremost: library authors, of which the vast majority is unpaid) unequivocally needs more time to digest this huge change. The fundamental pieces needed to even attempt nogil support are barely starting to be ready (and some are still just on the horizon, like being able to specify nogil-only dependency constraints). But what we actually need is for libraries to build on top of that, publish a first version with nogil support, get feedback what’s broken, etc. before we can determine the real impact.