@Mark great point, though we could actually do the same for the node name couldn't we I suppose? And that would mean that we wouldn't be impacting our current code for EIS name in favour of this new functionality
The AS can have a file that says
"David's" prefered name TS node name
----------------------------------- --------------------
"foo" 1
"bar" 2
"baz" 3
Basically it works a bit like a bespoke form of hashing where the hash of the remoting identifier is manually specified in some file, as you suggested above basically but for node names rather than EIS names.