I've never bothered with looking towards another.. do it yourself, collaborate, experiment, that is the key, as long as you can

I hope tictac can work out how to disable the chosen core upon boot method, which failed for me, it would be of great help.

I have an old idea roughly plotted, for PCs to include a separate loader and hardware tester/initializer which is what the BIOS now does, then straight after that load up a tiny DSL-like environment overclock and test tool such as AOD, but customed to replicate the mass DFI BIOS OC options. This being a separate code development able to be ran through a peripheral attachment such as USB (mainly a tiny programmable SSD [sub1GB]) and not part of the BIOS, but the BIOS having the option to enable or disable it. I am talking minimal time delay between the BIOS loading and this tool loading straight after, stripped down, no eye candy.
Then, using that software, we choose to load whenever we oc straight after the BIOS, we can have core0/1/2/3/x.. at 0% load in them (unlike in the BIOS), idle, downclock, disable and start clocking and working out full stability before the OS loads. A tool with a combination mixture of EVEREST/AOD/Prime95/Memtest/DFI BIOS. It will need a basic SPi/WinRAR calculation tool inside it to verify if oc parameters have changed, two stability testers for CPU/MEM (maybe 3rd for GFX, but that would get lengthy and complicated) and the obvious hardware feedback mechanism. I believe it would work wonders for oc'ing.