there are exceptions like tether that don't have a network of their own and rely on bitcoin network. when you send tether you are actually sending them on bitcoin blockchain and to a bitcoin address so it makes sense that the address is the same.
It makes good sense if you control the private key, normally this is not an issue while using wallet because people can decide to use noncustodial wallets but I still see it to be an issue while using exchanges that your private key is managed by the exchange. Also, many people are novice and make the mistake in a way they may not get the tether back by sending to an address they do not have its private keys.
I think something can be done, in a way to invalidate tether omini addresses while mistaken for bitcoin addresses. All needed is a little more of programming and testing.
If we remember the litecoin nested segwit addresses that started with 3, people also mistake it with bitcoin and has resulyed to many bitcoin been trapped and lost, but litecoin developers was able to create the M-ptefix version of the address with the same private key as the 3-prefix. That aside, also the address is not valid while mistaken for bitcoin address (although, I read this, not yet in my practical).
I am not certain, but I think there is something developers can do to make this work. Although, I used litecoin as an example, but not a perfect example though, but when not yet implemented, it can make people think such many not be possible.