Is it? We don't use it for any of the 40k+ desktop or mobile devices we manage.
Same with all the vPro stuff (which is kinda related but not completely).
We do use Windows autopilot though but that doesn't depend on IME.
That still doesn't really give it any reason to have it in workstation chips, in Xeons perhaps...
>but why the hell would this tech be put inside consumer devices?
A:
>It just sits there as an exposed attack surface
Because it is cheaper to make one single CPU chip variant, that is then sold to both the corporate and consumer channels, than it is to make two, one with ME for the corporate channel, and another without ME for the consumer channel.
Plus, once the ME was required to actually boot the CPU (note, why it became a requirement is a different argument), it then became much more expensive to omit for consumer grade CPU's because a "non-ME consumer grade" CPU would need to be a completely different chip with some alternate way to "initially boot up".
It's incredibly useful for companies and organizations, especially when lending computers to their employees, but why the hell would this tech be put inside consumer devices? It just sits there as an exposed attack surface without the user even having the tools to maybe make something out of it.