If you commit changes after a rule change, the management server pushes the new rules at the next heartbeat interval. (By default this is set at every 10 seconds). If you don't commit changes, then the new rule is pushed on the next client configuration request which is by default set at 1 min intervals.

The only place I could foresee this being an issue at all is where you have servers across a slow link so you set the configuration request interval up to reduce traffic…