Stockholm (79 ms ping):
Frankfurt (89 ms ping):
As in 2 years of using he.net tunnels I didn't find any practical advantages of that (apart from greatly increased time of apt-get dist-upgrade), the solution is obvious.
Pick a provider that has an upstream that IPv4 peers with Hurricane, if not native IPv6 peering so that you can get native IPv6?
Either of those solutions will help reduce those relatively large ping times. I'm assuming you picked them because they are actually the closest you could pick.
The primary purpose of the tunnel broker service is to provide IPv6 connectivity for software developers, network engineers, and technologists, so that they can do testing, development, and experimentation, in a situation where a native IPv6 solution is not available.
And now, due to happy eyeballs being included in modern browsers, you can even leave it on all the time and whichever address family (IPv6 or IPv4) is faster will be the one that is used.