It may just be that by selecting a 212 instead of a 206 you are dividing by half your real soft-current limits (both battery and phase), so it may be this that makes it looks "fixed"? To really be sure, you could select the 212 as controller type but double both current limits as when using the 206 setting - both results should be equivalent.
The transistor-based current overload circuit signal is independant of firmware, so programmed values should not directly affect it... unless using the 212 and 218 settings makes the firmware ignore the overload signal possibly? But then, why would they populate the overload signal parts on their 212's?
I quickly re-programmed my modded 6fet (with soldered shunt) to try this last night ( so I havent done any real testing with it ) programmed current was set to 20A and phase current to 60A , Before re-programming the controller would cutout and the watt meter peaked at 10A (as virgin 6fet ) after re-programming watt meter peaked at 12A and no sign of cutting out ( this was with no load on the motor ). My thinking is maybe the board selection in the software is that one of its functions is to delay the hard cutoff for the type of controller selected... If all the controllers have all the same values of components then the only thing that can change it is the sofware because my 12fet works ok .