I'm using brains OS for about an year, want to say thank you to developers. it is pretty stable OS.
the issues that should be addressed ASAP:
1. temp cut on 95C - it is not good, as under high overclock it is ok to run 95-100C, so this should be tunable from GUI: "fan-dangerous-temp":"100"
default should be: 100C
2. the same as above but for "no-sensor-scan":true - should be a checkbox in GUI
3. in case some hashboard failed the order of OC settings are shifted, Example:
if i set:
board#0 = 750 freq 8.8V
board#1 = 700 freq 9.0V
board#2 = 725 freq 8.9V
if board#1 - failed then board#2 will get "700 freq 9.0V" settings from board#1 - this is incorrect and brings problems on healthy boards. please fix this asap.
Actually the presets are just rough guesstimates. Not all S9s are the same, certainly not all hashboards, not even from the same batch and model.
In my opinion, they wanted to go err in the safe side. It would be nice if they added those config options to the gui, but its not the end of the world. These are the types of settings that if you cannot bother to edit a simple text file to change, maybe you shouldn't mess with them in the first place. If it were me, i would even remove the ability to change frequencies from the web UI so be glad...
"high overclock" as you call it, is actually less efficient than a good underclock. bOS is very manual config oriented and it lets you do whatever, but you are really nitpicking here.
Most people should not be overclocking, period. 95°C seems to work fine for hundreds of units in a tropical 40°C ish ambient temp location, only a few units with buggy sensor readings need the setting changed, same as with "no sensors scan" which is an overkill choice only for very specific situations. Most people should NOT be using those.
Only your third issue looks important for consideration in my opinion, but i'm not sure much can be done about it. Perhaps reset frequencies to default if the number of hashboards change?. I don't think each hashboard has an unique ID they could use to prevent that. If there is, maybe this could be addressed.
And remember, nothing in bOS is changing until after bosminer is fully released to replace the (abandoned) cgminer, and only then would the work (hopefully) restart for new hardware and features...