TYPO3 Core

Why jumping through hoops, checking if we can find a class file (buildClassLoadingInformation) if we could know beforehand, that the class name is invalid and exit early? We could get rid of all try/catch and clearly behave like the PHP class loader do nothing at all and return early.
In fact PHP should not call an autoloader for invalid class names as the language should know about that, but as of now, we have to deal with it.
I mean several people proved, that this change has virtually no impact on performance and we still prefer a complicated solution (several try catch, trying to resolve class paths for classes that cannot exist) over a simple one (exit early)?