Unfortunately, regarding the use of port 80 there is absolutely nothing that Microsoft can do. Port 80 is the standard port for HyperText Transfer Protocol (HTTP). As such, every browser "knows" that a URL that doesn't include an explicit port (e.g. http://myserver.homeserver.com:8080) should be requested on port 80. This happens on the remote client, not on the server, so it is out of Microsoft's hands. Until Internet service providers stop blocking port 80, this issue will continue. We don't have to like it, but complaining to Microsoft is the wrong tactic. Complain with your wallet instead: choose an ISP that doesn't block the ports you need and tell your current ISP exactly why you're switching.
Regarding DHCP and port forwarding, if you are not using UPnP for your port forwarding (I don't) you must either A) use a static IP address on your server (I do), or B) reconfigure port forwarding if your server picks up a different IP address from your DHCP server after a reboot. Again, this is outside of Microsoft's control; they have supplied a mechanism in WHS (UPnP router configuration) which for most modern consumer routers will automatically configure the router successfully. If it doesn't, it's the router that's at fault, because it claims UPnP compatibility without full UPnP support.
I'm not on the WHS team, I just post a lot. :)
