See AMD's SSE5 vs Intel's SSE4 conflict in x86 - both have instructions that the other doesn't have, and some that both have, and, from what I understand, even the instruction formats conflict.
One cannot easily make an x86 extension because there are approximately ~3 entities on the planet allowed to make x86 extensions.
I wouldn't be surprised if Sony/Microsoft did too for their consoles.
It's doable if you have enough money to get AMD or VIA to make you a one-off.
There is the idea of profiles, i.e. a single nice name for a group of extensions so that there's something one could provide a precompiled binary for, but I don't know what, if any, are RISC-V's plans for that.
Profiles. See RVA22.
It'll likely work much the same way for RISC-V, eg. in Fedora we require that the C (compressed) extension is supported, otherwise the distro won't boot, and things like the vector extension will probably be used only by specialized math libraries and the like.