When the user applies a kubeletconfig the created "99-worker-generated-kubelet" MC that gets generated changing the "nodeStatusUpdateFrequency" and "nodeStatusReportFrequency" to 0s. The kubeletconfig does not have these values mentioned in it. These values are getting enforced by the MCO somehow. I reproduced the issue with version v4.12.36 but i can see this issue exists on 4.12.19 too.

RHOCP v4.12.36

Just install a cluster of version v4.12.36 and apply a kubeletconfig.

1. Install a cluster on version v4.12.36
2. Create a simple kubeletconfig like below:
~~~
apiVersion: machineconfiguration.openshift.io/v1
kind: KubeletConfig
metadata:
  name: worker
spec:
  kubeletConfig:
    maxPods: 240
  machineConfigPoolSelector:
    matchLabels:
      pools.operator.machineconfiguration.openshift.io/worker: ""
~~~    
3. Check the kubelet.conf file contents in the 99-generated-kubelet MC that will get created from MCO. It will have inside the "nodeStatusUpdateFrequency" and "nodeStatusReportFrequency" set to 0s.     

The "nodeStatusUpdateFrequency" and "nodeStatusReportFrequency" are set to 0s whithout the user to specify them.

The "nodeStatusUpdateFrequency" and "nodeStatusReportFrequency" should stay the default 10s and 5m respectively.

This is causing issues applying a Latency Profile as the latency profile will create an MC of lower priority "97" and the "nodeStatusUpdateFrequency" and "nodeStatusReportFrequency" values will not get updated.