I do understand the enterprise world, having come out of the big iron Unix scene and enterprise software planet too. One of our larger clients built appliances from our products. Indeed I see where you are coming from.
It was impossible to see where you were coming from in your opening post(s). Essentially you said:
I thought I would post my script so others could play with it, enhance it, etc... I would really like to see it be part of the base install someday.
In that vague context my comment stands; I don't know about you but I find it often difficult to read minds when very little information is presented, consequently sometimes I don't bother trying.
As for "hostname", which one? A server may have multiple NICs, multiple IP's (real and aliased), each with PTR records which mean more potential hostnames.
My gut feel is that inventing infrastructure to do this one thing won't find acceptance, because "hostname" is but one parameter that might need to be considered.
With > 20,000 ports, each of which having its own configuration approach, coming up with a common approach seems... difficult to envision.
Some orgs and companies have made a business out of *nix automation and configuration management - i.e. the popular "control panels" found in commodity web hosting environments.
In my current world hostnames don't change very often at all; and even when bringing up a new machine, the hostname data and assignment task itself is 0.0000009832% (approximately) of the data and scope of change that I might face. I have written some configuration automation software to help; and even more docs; but I find the situation still far from "press a button" ideal.