Why don't you get a netbook-grade computer or one of those MINI PCs that can be had for (last I checked) something like $100 or $150?
(Another idea is to get a computer with broken cooling, or play with the fans off, so that the CPU will throttle if you push it too hard, but then you risk damage from overheating if you're not careful.)
My bedroom computer is a mini pc, equiped with a Intel i3 7100u, wich is a laptop cpu. I might open a dedicated thread once I finish the 3D printed case, eventually.
I also have a tablet equiped with a Atom z8350, and to be honest is the best "gaming" experience I had in years. I've even manage to finally beat the 6W hard limit, wich means if you increase graphic options, the CPU will throttle. Now it's able to do 8W+, don't seem like much but is a substancial % increase.
Thanks for the tip but is quite easy to throttle modern-ish CPU speeds by playing with the "governor". In Windows this takes like 10 click to do, in Linux should be easy but is outside of my limited knowledge. For anyone interested on Windows 7 and 8.1, the governor is located on energy scheme (balanced is good) advanced options.
I do remeber from a previous thread your computer had a broken cooling, have you been able to fix it?
For me, it's just another way of navigating a backlog. ;-)
Personally, only play on Ultra older games but that is very smart. It's usually very hard to resist playing a new game though...
(Note: Using Linux here, so the programs mentioned here are Linux programs.)
Still haven't tried to fix it.
I've been using the cpupower program to limit the CPU speed to 1.4GHz, which works fine if I don't do things that are too taxing; if it's overheating, I can lower the maximum as low ad 800MHz, which is usable with patience, and is definitely more usable than the ~230MHz that it throttles to.
Another useful trick is to use the pkill command to send the SIGSTOP signal to processes that are eating a lot of CPU (like chromium at times); this prevents chromium from using any CPU at all, so the system has a chance to cool down, and I can then just send it SIGCONT when I'm ready to have it run again.
Incidentally, compiling isn't entirely CPU bound, so during the time the computer is doing disk I/O, the system has a chance to cool down a little, delaying the time when it throttles. (One interesting question I have: For long running tasks, is it better to run the CPU at high speed and have it throttle, or will the job complete faster if I lower the max CPU frequency to prevent (or at least reduce) throttling? I've heard about the "race to idle" approach, but that assumes that the system doesn't produce enough heat to throttle.)