I think you're mixing two different aspects of the Tor project. On the server side, onion services (running a tor daemon that reverse-proxies request to your H

I think you're mixing two different aspects of the Tor project. On the server side, onion services (running a tor daemon that reverse-proxies request to your HTTP/mail server) provide end-to-end encryption and secure name resolution (transport security). On the client side, the Tor Browser is a custom Firefox edition that aims to make user fingerprinting impossible among Tor Browser users. From a server's perspective, they are all the same; they also come from the same IP address (the Tor exit nodes) when the service is not an onion. Enabling an onion service does not prevent 3rd party tracking although it raises the bar. Third-party scripts/cookies can still do plenty of tracking. That's why those (as well as web fonts and SVG) are disabled in Tor Browser's Safer security settings, and javascript is completely disabled in the Safest mode. So fingerprinting protection really is taken care of on the client side. Neither onion routing nor onion services will help you evade tracking if you use a classic browser.