I have no idea, but I suspect each language takes a lot of space on drive, and having "all languages" supported in one device is over-the-top expensive for most use cases. I'd suspect they would come out sooner or later with a "current locale langs" or "currenct keyoard langs" supported.
My implementation intersects between a Set of my wanted / suspected / expected languages and the VNRecognizeTextRequest's
supportedRecognitionLanguages
As mentioned, currently this seems to be only US english.
Literally billions of non-english speakers would benefit from an OCR service in their native language. English speakers would benefit from an OCR service when abroad.
Some apps' feasibility would depend on whether VNRecognizeTextRequest supports only the current locale lang or the current keyboards langs, or somwhow deduces langs from current location or something else. Having no langs but en-US at this stage would probably drive many developers to opt to use the googpetition or another cloudy OCR service from the get go and forsake VisionKit... I'm considering this.
Some OCR implementations would definetely benefit from having OCR languages support added / removed "by demand", so that LocationServices / user preferences / location by ip services could allow better chances at detecting texts for users WHEN ABROAD, which is... hmmm... a time where I suspect OCR / Translation would have many use cases and would be in high demand.