... also you don't get reverse dns with 6to4 ...
Not true -
https://6to4.nro.net/ is where one registers it for FIXED IPv4 (and thus fixed 6to4). It's been around for 3.5 years. Now, granted that there really isn't a DNS reverse zone for dynamic 6to4 (where the IPv4 is dynamic), but that's not even universal for IPv4 itself. I still get plenty of web page requests (both v4 and v6) that have no reverse.
Here in Los Angeles (btw, it's one of HE's peering points - at LAIIX), the "network nearest" 6to4 gateway appears to be in Amsterdam, yet geographically, Micro$oft's 6to4 gate near Seattle, WA would be the geographic nearest. LA, being the second largest peering point (actually, 3-4 points as there are that many exchanges here) and population center in North America should have its own gateway (and so should NYC at NYIIX). I use my HE tunnel only for NA and Asian/Pacific routes, and still use my 6to4 for European routes because for some reason, it usually has RTTs about 5-10ms
less, but not always. I did not test South America or Africa because I have no regular traffic headed that way.
I can see some benefit in having a local tunnel over 6to4 (lower RTT), but only because 6to4 is poorly deployed, especially in North America. I believe that everyone assumes that everyone-else will deploy such gateways. In contrast, also note that two 6to4 hosts will end up using the direct IPv4 path between them if properly set up ("2002::/16" -> dev sit0 [or whatever the encapsulation interface is called on your system] with NO gateway), while two IPv6-tunneled hosts will have usually longer routes - each to its tunnel's other endpoint and the distance between the two tunnel brokers.
As far as those who do have dynamic IPv4 assignments that don't change often, consider yourself lucky. My DSL assignment at home (not my co-located server which has my tunnel) does seem to changeabout every 10 days.