As for different DVCSs, I think you're exactly backwards. Almost everyone commenting on these things seems to believe that git isn't special, it really does the same thing as every other DVCS, etc. And on a fundamental level this is true: it's very easy to convert from one DVCS to another, because fundamentally the models are so similar. git just exposes the model in a more obvious way. The insides are the same, the outsides are different.
But--try to find a sentence like "Mercurial and Git differ only in nomenclature and interface." in the CvsConcepts page.
I've yet to do a lot with Git, but your post has made me a lot more interested. After wikipediaing the features, I'm starting to see how one could save a lot of time by building an app on top of Git rather than recreate all this functionality from scratch.
There are plugins for Mercurial, Bazaar and DARCS.
https://git.wiki.kernel.org/index.php/Interfaces,_frontends,...
Git to Mercurial.
Git to Bazaar.
http://doc.bazaar.canonical.com/migration/en/foreign/bzr-on-...
It doesn't seem other DVCS are that incompatible.
Do you have any examples of people (other than you) who have actually done this? It would make your argument much more convincing.
Also, the fact that other DVCS's have different, incompatible models underlying them suggests that Git's nouns and verbs are not nearly as universal as Unix pipes. If Git's nouns and verbs were universal, Git could subsume other DVCS's (ie. you could implement other DVCS's semantics on top of Git with performance as good or better than what they have already).