> SRV could be modified in a different spec instead.

I don't think it could be, at least without breaking things. Unlike SVCB, SRV wasn't designed to be extensible, so adding new functionality can't really be done without breaking anything that currently parses SRV responses.