Go x86, and you'll end up dealing with Intel, or AMD (okay, there's Via & maybe a few makers of legacy x86 parts).
Go RISC-V, and roll your own or pick from a growing list of vendors, are both valid options. And switch supplier while keeping your toolchain ecosystem.
I'd expect at least that this will spur innovation in the field. Likely increase consumer choice.
More suppliers of [insert product type here] is almost always a good thing.
And the specs extend further to non-ISA, such as standardizing boot process and platform.
If that is what you're saying, I think you're wrong.
As to the low level hand coded assembly. There's a fair amount of stuff in the Intel architecture that's not officially published. There are tools (from Intel) like VTune and the Intel C compilers that use non-published interfaces to optimize C or assembly, sometimes significantly. It is true you can write software without them, but many people purchase these Intel tools to make sure their systems run quickly and efficiently.
I can't remember if the SiFive U-X4 core equivalents were defined in the open RISC-V specs or as part of SiFive specific interfaces. If the former, then your point is even stronger. If the latter, your point is still valid, though modulo the impact of having relied on a SiFive specific interface.
But yeah. Even though we have compilers, it's not like you can spin up support for a new ISA in the drop of a hat. If you launched a project with a StarFive part and then decided you wanted to use SiFive IP, you should be able to use the same tooling. The impact of that shouldn't be under-estimated.