Hi TDice, thanks for taking the trouble to report to Feedback Hub. I'm no longer afraid to click on an aka.ms link -- after spending the time required to determine that it's a domain controlled by Microsoft USA -- so I clicked on your link, but got an unhelpful response.
I hope you'll take the trouble to post an update here if you get any response from Microsoft. It'd be nice to know if they're at least acknowledging the issue. It has overheated my laptop only once AFAIK. I tried to diagnose a bit using procexp and procmon, and by looking for a logfile in the immediate neighbourhood of the PhoneExperienceHost.exe which was hogging a CPU core. Curiously: it appears *not* to be bashing at the file system or the registry, but is instead just bashing at main memory -- but without a big enough working set to be making much forward progress at bitcoin mining. If the process running this exe were "merely" busy-waiting on a signal from another process that has timed out or been terminated, then I can't see why it'd have 28MB in its working set... and if it were trolling through my filesystem to discover phone numbers and accompanying PII in my files (even though I have never knowingly given it permission to do such a thing), I'd see the filesystem activity with procmon. So ... it's not your run-of-the-mill CPU hog... so I'm *guessing* it'll be impossible for the QA team at MS to localise until they have a bit more to go on than individual Win11 installations which (for whatever reason) are exhibiting this defect after (perhaps) a prolonged period in some half-sleep mode after the monitor-darkening timer has kicked in...