There are many ways to view these forums, I tend to view them as help forums, If I have insights that can improve your folding experience, I share that. If I know less than you do, I try to stay out of the way and let others help.
There is a gotcha coming that I hope the development team is preparing for.
Years ago Sony wrote an Android port for F@H and just after that development, ARM invented a new technology that maimed their project.
In an architecture called big.LITTLE some number of simple, power frugal cores are included with some advanced power hungry cores on the same CPU.
There are actually 3 different versions and the rules change for each. F@H works with some but others were particularly difficult to code for.
1. You have some number of LITTLE cores and the same number of big cores, and if any program needs a big core, all the big cores replace all the LITTLE cores.
2 You have some number of LITTLE cores and the same number of big cores, and if any program needs a big core, that one LITTLE core is replaced by a big core.
3. You have some number of LITTLE cores and some number of big cores, if any program needs a big core, it is shifted to that big core, but all LITTLE cores remain active.
3 is a particular problem for F@H as the number of active cores varies over time and some cores are wildly faster than others. F@H is not currently written to cope with either issue.
Sadly for F@H, Windows 11 includes a scheduler that allows big.LITTLE, both in ARM and in x86. This will bite F@H code that has worked well for decades.
The simple, least appealing solution is to quit CPU folding. It would be far better to program F@H to only fold on big cores. Ideally, you would run one slot of LITTLE cores and another slot of BIG cores, so each WU only sees equally fast cores.