This message was deleted.

Not sure it helps, but Ive had a similar issue with wmipriSE using high CPU on 2016 and 2019 hosts. Spend hours and hours trying to figure it out but in the end used WEM to control the process (cpu priority and clamping are available). All fine.

Yes I was thinking about WEM too, but we don't have that at the moment. Maybe we can do something similar using ControlUp automation. But still, I'd like to find out what's causing this issue.