They were mandated to create a scheme in isolation on a deadline, without having input either from navigation apps or from consumers, and without any requirement that web browsers or other operating systems would need to support the same scheme.
As another comment pointed out - it doesn't work. Websites and apps still integrate with a navigation product directly, rather than use this scheme. And why wouldn't they? Even if it was launched worldwide on iOS, it still is just a defined subset of any particular navigation product functionality. It also is just yet another navigation option to integrate into your platform, since the feature still wouldn't be available on desktops/Android.
Until everyone is sitting at the table wanting to work towards interoperability, the feature simply can't work. So why perpetuate a broken chooser into other markets?
Self-imposed isolation and deadline.
> without having input either from navigation apps or from consumers
Because Apple never asked either navigation app developers or consumers since "Apple knows best" and spent several years fighting DMA instead of implementing these features.
> Websites and apps still integrate with a navigation product directly, rather than use this scheme.
Because there was no scheme to begin with, and when Apple finally relented and made it, it only made it available in the EU.
> Until everyone is sitting at the table wanting to work towards interoperability, the feature simply can't work.
Yes, Apple doesn't want to sit at the table to work towards interoperability.
Apple Maps was made default on iOS in 2012. They literally only implemented the "scheme" last year, 13 years later.
DMA entered force in 2022. Apple had known about it coming for at least two years before that.
And even without DMA that would be a proper thing to do to begin with which they had to be forced to do by government action.