Right, which is why you should use a privacy respecting search engine. Can’t ditch Google? Use a metasearch engine like SearXNG. Some of SearXNG’s instances have no issues with Google searches, like https://paulgo.io/ which I have been using for sometime now.

By default, arkenfox’s user.js disables the suggestions you get while searching using the search bar on home page and location bar. I have re-enabled it.
file.io only provides temporary storage, but I didn’t expect it to delete my file before the said date. I have uploaded it on wetransfer this time, here you go: https://we.tl/t-3rn02cSnBA

Both are safe and privacy friendly from what I understand. It is just that I am more habitual of Greasemonkey on firefox now and it is pretty good for me which is why I recommended it. I should have mentioned both Firefox and Chrome in Violentmonkey’s parentheses, which I will now.

I have added comments in my user-overrides.js exactly for that purpose but I can still give an overview.

• I have enabled some of the pages disabled by default in arkenfox’s user.js like the home page, set new tab page to use home page instead of throwing a completely empty tab and such.
• I have enabled search engine updates, defaulted the download directory to OS’s default download directory (for e.g. ~/Downloads in most Linux distros), enabled the search on location bar, enabled find as you type functionality, enabled search engine suggestions, make the chrome(like the home page and such, it doesn’t affect the sites because of resistFingerprinting) use dark mode by default and more.
• I am forcing AdGuard DoH with fallback to system DNS disabled, you can use any other DoH of your preference by just replacing the URLs in line 14 and 15 of my overrides.
• DRM is enabled for the sake of sites used by many people, like Spotify, Netflix
• There’s a pref in arkenfox’s user.js that breaks some video streaming sites, network.http.referer.XOriginPolicy, which I have set to 0, i.e. the default in firefox, and would recommend using Smart Referrer extension with strict mode and whitelists disabled instead because the extension can be toggled off on the go if some site breaks because of it.
• enabled developer tools inside browser context.
• disabled resistFingerprinting’s letterboxing.
• Done some optional hardening which includes disabling ETP web compat(can break sites like Facebook), JIT(don’t worry, extensions can still use JIT because of a certain pref), ION, webassembly and asm.js. all of these except etp web compat, mostly only impact the performance of JS on sites, and I have hardly noticed any performance drops. I had to do it because of the security issues related to these JS performance improvement technologies. Arkenfox’s user.js’s comments have included links for more information about security issues related to these.
• added quality of life additions from Kellegram’s user.js, which includes changes that should make the scrolling experience much better than compared to the default and a few more stuff.
• there’s more small stuff which you can read about from arkenfox’s user.js’s comments and my own comments.

As you can tell, most of my changes are related to convenience, looks, optional hardening, forcing a few prefs and such. You should definitely give it a read after arkenfox’s user.js. I apologise for the late reply.

Out of curiosity, how do these flags, the ones I mentioned in the post, affect the fingerprint or whatever measure you are using to suggest uniqueness?