Rather, harmony seems like an interesting side effect generated when Fog Creek built some swank tools for mercurial-based corporate developers, and git won the war while they were doing so.
Most of the value I see in Kiln is in the activity filters, the notifications, the code review tools, the ACLs, and FogBugz integration. Git/Mercurial interoperability is just a cute feature.
"I like their tools, but does it support git?"
Now, the answer is: "Yes, it does."
I'd say that's a tad more than a "cute feature".
Fog Creek's emphasis on how they achieved git support steered the discussion to be about the value of git/hg interoperability, rather than the value of Kiln for corporate developers. And it seems like the consensus is that git/hg interoperability is, at best, a nice-to-have.
So, still no money from me, unfortunately.
I guess you could just not use the feature and only use git clients. Who cares if the redundant hg clone they keep on their end gets out of sync.