Then you're making a serious mistake.
If there's more than one process that listens on an HTTP-over-Unix socket, and they both start up with your desktop session, then they will both write to unix.hosts. That's a race condition. unix.hosts *will* get clobbered on occasion.
At the very least, the spec must mandate which file locking API to use when reading or writing unix.hosts, but why go to the trouble when symlinks are inherently atomic?