I can imagine situations in which a developer wishes to create a composable token covenant and not care about giving it a specific ticker or an image.
IMO, the KCC20 spec should not enforce an on-chain identity.
A token (or any covenant for that matter) has a unique cov-id which is its true identifier (much like a contract address on Ethereum).
So yeah, I’d go with a different standard.