This is one of those things that sounds really easy but would just be a ton of work, and Lemmy is just 2 devs afaik. How do you know this query parameter is a tracker vs something required for the page? There's no way to know programmatically, so they'd need to maintain a list of known bad parameters - and even then those are probably site specific. What if one site uses the query parameter as tracking and another uses the same name coincidentally and it's a part of filtering or sorting?

This sounds like a better task for a browser extension or an npm package they could consume instead, rather than it being a part of Lemmy itself.

Keep in mind that this is the Lemmy.World support community, not Lemmy in general, so this post may not be seen by Lemmy devs.

If this was implemented, I doubt it would make it as a core Lemmy feature. This would like have to be built into either clients/interfaces (obviously each one would have to do this one their own), or it would probably have to be built on top of the planned upcoming plugin system.