Restrict KIST parameter range and make a separate client param
Network parameter KISTSchedRunInterval is allowed to be between 0 and 100, with the idea that 0 disables KIST, and 1-100 are interval values in ms. However, the code path to disable KIST via this param is broken due to additional safety checks elsewhere, and 1ms drives relays into 100% CPU loop.
We should change the allowed range of this param to be 2-100 (though 100 is awful high).
While at it, we should make a separate KISTSchedRunIntervalClient param, so we can control client and relay KIST values separately.
Edited by Mike Perry