I think it would be possible for BitDNS to be a completely separate network and separate block chain, yet share CPU power with Bitcoin. The only overlap is to make it so miners can search for proof-of-work for both networks simultaneously.
The networks wouldn't need any coordination. Miners would subscribe to both networks in parallel. They would scan SHA such that if they get a hit, they potentially solve both at once. A solution may be for just one of the networks if one network has a lower difficulty.
I think an external miner could call getwork on both programs and combine the work. Maybe call Bitcoin, get work from it, hand it to BitDNS getwork to combine into a combined work.
Instead of fragmentation, networks share and augment each other's total CPU power. This would solve the problem that if there are multiple networks, they are a danger to each other if the available CPU power gangs up on one. Instead, all networks in the world would share combined CPU power, increasing the total strength. It would make it easier for small networks to get started by tapping into a ready base of miners.
Namecoin (NMC) implemented your proposed BitDNS in a better method in 2011. I am sure you are aware of this

I implemented "BitDNS" into Denarius (D) recently, I was able to complete full integration by hooking into the chain with a separated name database by utilizing the asm OP_DUP OP_2DROP etc. I know you said 1 TLD .web was a good idea, this will be added in the future, it is trivial. Denarius currently supports .d, .dnr, .denarii, .ipfs, .king, .sys, .btc, and .bitcoin TLDs. This "NVS" can be extended upon similar to Namecoin for things like text, magnet links, name aliases, and really data of any sort. The value of the names can handle roughly a limit of 20kB.
If you want
http://satoshi.btc/ or
http://satoshi.bitcoin/ just let me know. I thought .btc and .bitcoin were a bit more fitting for decentralized domains and a good option from the current .bit.