I do not see why this is an issue. From ssh point of view I can always use a stable name like foo.example.com or bar.intranet.example.com. How such name is turned into a connected socket inside ProxyCommand does not matter. And if one wants a convenience, then one can always use something like:
Host foo bar whatever
ProxyCommand %h ...
where the first %h will be foo while the second %h feeds foo.example.com to the proxy command.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds