You can customize and de-fingerprint simultaneously. I just got a totally disposable browser to come up configured the way I want it, the first time, with no old profile being used; it is, in other words, becoming what I want the first time it’s run. And it has the arkenfox fingerprint stuff and other “hardenings” from his setup.
In short outline:
- Create a template with a fresh firefox install on it.
- Create a dvm template based on that.
- Start up firefox in the dvm template.
- Set up firefox the way you like it–do nothing else.
- Grab the .mozilla/firefox/aaaaa-/prefs.js file from that machine and copy it somewhere else. The aaaa will be the profile name that firefox set up for you. There will likely be two of them, one will be empty, the other will have -esr in the name.
- This file will be full of a lot of cruft, but you can experiment with removing things from it and then dropping it into the same directory on the dvm template (not the disposable) but name it user.js when you do so. Running firefox in disposables should let you see what the effect is.
- Later on you can treat this file just as if it were the arkenfox file (or you can even just append your stuff to a copy of that file), turning it into a firefox.cfg file and installing it on the temple (yes the template) as described in here: [Guide] Automatically install extensions and configure new (dispvm) Firefox profiles with arkenfox user.js and policies
NB: You cannot set the default browser in this way. The best I was able to do was set up the separate search bar, deactivate searching in the main URL bar, force it to only show my favorite search engine as a suggestion. But in the separate search bar, it still defaults to google. You will have to follow the instructions about policies in the link, and further down in the thread is the actual policy that will finally drive a stake through google.