Oh yes! My brand new macbook pro had been sitting at 300% kernel process usage ever since I bought it. I thought it was just ridiculously badly optimized. Why doesn’t the system inform you when it’s spinning it’s wheels with no work just to cool down it’s chassis?
I think that’s sort of what the kernel_task usage is now: it’s minimally documented, but I guess the scheduler is now designed to attempt to throttle the system it it’s overheating.
pmset -g thermlog