We made obsolete the EditorPrefs path for ScriptableBuildPipeline settings as these were global and not per project. We adopted a json file settings approach a few versions back, loading the old values from EditorPrefs first then loading from the json file as an override. This works for the initial upgrade path, but if the json file exists with valid settings and the user keeps using the EditorPrefs path, those new EditorPrefs values will not be used.

It was also raised that the static settings properties in the class ScriptableBuildPipeline were not made public. So these need to be made public with setters that trigger SaveSettings() on value change.