I think at this stage of the game most Librem 5 users won’t care whether configuration has to be done using a command line interface rather than a GUI, or has to be done directly in dconf-editor, as long as there is good documentation over what needs to be done.
That’s the thing. If you have n on-off switches in the configuration then there are 2n sets of settings to test - and that rapidly becomes “never going to happen” - and some sets of settings just won’t work even when they do get tested - so it becomes difficult to understand for users and poorly documented.
That means configuration options are ideally specified to be “orthogonal” i.e. independent in function, and ideally independent in implementation, to reduce interactions in the code.
As an illustration of the challenges, on the iPhone, with suggested completions out of line, the first completion is usually what you typed even when it is not in the dictionary and touching that has the effect of suppressing auto-correct i.e. I am typing a word that is not in the dictionary and I know what I am doing.