Review of frequency-rt branch prior to submitting PR upstream

Ok.  This web UI will need to work across both frequency and non-frequency updates, though.  If I understand you correctly, isn't this removing the delay information from the web UI for non-frequency real-time updates?  Is there another way you could handle this, so this value isn't shown on frequency-based updates, but is still shown for normal delay values from non-frequency-based updates?