Consider lowering statestore update frequency further or adding jitter to admission controller

We could consider reducing the update frequency further (maybe just for coordinators??) and possibly adding some jitter to the admission process to prevent overadmission when multiple queries are submitted at the same time to different coordinators.

The problem is that the coordinators independently make admission decisions before the change in state from previous decisions is propagated to other coordinators.