Only a little bit better as adding ten prefs one by one, would be your original first approach to this preflist project: add them as a little list at the end of the profile prefs.js, while the browser is closed, then restart.
Or there's always user.js, which enforces prefs at every startup, but that my be too restrictive.
What would be interesting, where do the 'automatic' values come from?
By the way, would like to share a general idea for all people using their own pref lists. Would you sometimes like to see in about:config little comments, what some of the prefs and values are about? Since awhile I'm very happily adding self-written info-prefs :-)
Just a few examples, not perfect:
pref("security.tls.version.__INFO", "INFO: FF23+(KM7X) 0=SSL3, 1=TLS 1.0, 2=1.1, 3=1.2 since FF24, 4=1.3 beta");
pref("security.tls.version.__INFO2", "INFO: check available versions on about:support. TLS1.3 needs min NSS 3.3");
pref("toolkit.telemetry.__INFO", "INFO: Prefs NOT about collecting, only about SENDING! See profiler pref");
pref("profiler.enabled__INFO", "INFO: COLLECT data or not: Telemetry prefs only decide if they are SEND");
pref("dom.messageChannel.enabled__INFO", "INFO: for user identity / reCaptcha not clickable if false");
pref("dom.serviceWorkers.enabled__INFO", "INFO: MarioNET module for remote control (since FF44)");
pref("security.fileuri.strict_origin_policy__INFO","INFO: fileuri/checkloaduri: If websites can load resource-links. Check on browserleaks.com/Firefox");