As an update for everyone, a PR has been elevated. I've been also informed that this warning alarm is pretty much benign and it occurs only upon the restart of the SPMD daemon. Technical explanation is as follows:
There is no issue when the device comes up with fusion configuration for the first time. Issue is seen only when re-spawned with a new process id, which can be achieved by just restarting the SPMD daemon.
SPMD rtsock client is in stuck state due to processed ifstate ack is not 0. unless the ifstate that's acked is 0. rtsock client will continue to be in stuck state hence the alarm is noticed. Even though, ifsmon shows the states acked by SPMD is 100%, this issue is still seen. Looking further into the code to root-cause the issue.