As an optional parameter in the json it can be ignored until they feel it fits their needs. Only those who see value would need to adopt it.

I plan on using badges, but for instance, game clients from the 2000s have somewhat low character limits, so I was planning to have all users be unique nip-05 on my platform and use it to limit characters. Then they would get badges anyway on the npub, but with the ability to display aliases, sites could offer the ability to show all specified nip-05 addresses for all services, mine and others, that the user has registered nip-05 for. Allowing better identification verification.

It is not a question of if there are other more clunky ways to do it, but about streamlining it for better platform adoption and verification in a way that is useful to users and platforms