Yup, the new information seems to be more reliable.
Insider builds are more like beta version of Windows. Windows Core - seems like it is for some embedded systems, hence my confusion.
With this information I'd say everything is quite normal - standard Windows version, system is not resource-staved. Should work properly.
I'll wait for you to let me know how the fresh portable version is behaving freshly after unpacking. And possible some more information on when CH takes too much CPU and when it does stop doing that.
As additional help here - could you please check which CH thread is taking the cpu?
If yes, then:
1. Please install (or use portable version) Process Hacker (
http://processhacker.sourceforge.net/downloads.php )
2. Download the debugging symbols for CH 1.44 (
https://sourceforge.net/projects/copyhandler/files/copyhandler/1.44/chsymbols-1.44.zip/download) and unpack all the pdb files to the location where ch64.exe exists (the portable CH location). In the end you should have the ch64.exe and ch64.pdb next to each other.
3. Run CH and ensure it is taking much of the CPU without doing anything,
4. Run the Process Hacker and locate ch64.exe on the process list. Double click on that.
5. Switch to Threads tab and attach a screenshot here.