No, Nick, I haven't had to troubleshoot any 6t04 gateways and I think that's exactly my point. My ISP still feeds me the same IPv4 subnet that they did when I bought the connection in 1998, and they haven't even so much as hinted at the availability or interest in IPv6. My ISP? AT&T.
Verizon is implementing *NAT* to their consumer customers instead of implementing IPv6! In fact, I daresay, if we look at actual implementations ... outside of mobile devices nary an endpoint (except yours and maybe a few others) are using IPv6 addresses.
Given the choice between dual-stack, dual-stack-by-accident (which is where most organizations are) and IPv4 primarily .... where do you suppose the majority of organizations will continue to exist until forced elsewhere?
As for this comment: "What I am getting at is that if we can get more of us on board," I think you overestimate the numbers of who "US" actually is. Do not count me among the "US". I've been doing network architecture since the mid-1990s. I've lived, breathed, and overdosed on IOS, DNS, DHCP, SNMP, and a gazillion other network protocols. I'm fairly functional with IPv6, but not proficient.
Nonetheless, it's not difficult at all for me to see the lack of a compelling reason for any organization to dive into the IPv6 quagmire. And until that happens (along with motiviations to drop legacy Windows operating systems)..... you may be fighting the fight on the uphill side of the trail. :-)
To date, the best argument anybody has given for IPv6 is "we've run out of IPv4 addresses", but the truth is that such statements are hogwash. The only thing we've "run out of" is the ability to properly manage, control, and reclaim the dozens of Class A networks that were issued without prejudice in the 1980s and 1990s and are now used exclusively for internal networking --- or not at all!