FWIW the CPU in question is a 45nm dual-core, four-thread, 1,66 GHz Intel Atom chip that supports a max of 2GB of RAM. It was Intel's X86 alternative to ARM for phones/tablets.
Its micro-architecture was completely different and far more simpler and lower performing than Intel's Pentium or Core chips of the time in order to massively reduce die-size and save cost. Therefore it was slow and under-powered even back then in 2011, even without these artificial limitations put in place for market segmentation. Just ask anyone who used Atom chips of that era.
At the time you would often find these chips in cheap Netbooks and Tablets, usually by Asus, and running a bare bones Linux distro was the only way to get anything usable out of them, as getting run over by a bus was a more enjoyable UX than running windows on them.
In a way, those cheap, light, portable Netbooks were ahead of their time, held back mostly by the low performance of the low power chips of the era, the bloat of Windows of the era and the jankyness of bare bones Linux distros of the era that wouldn't ship with the mainstream apps people used on Windows.
So as cool as this hack of removing the artificial limitations is, I'm not sure how much this really helps to make a case for using this CPU for OS virtualization using Windows VirtualBox on all four threads, considering the already severely limited performance and RAM.