Bugged results can happen with any benchmatk.
Thing is we discovered that when using higher thread count than the cpu total, result ends up "bugged".
"In essence, the problem is that the M (64) threads are forced to run on N (4) actual cores, which the OS disperses into an incoherent mess, that can't be timed exactly. Basically, M > N is a recipe for inaccurate value in the Time field, which I guess happens as soon as M > N; all results with this number of threads are compromised.
One thing to note is that this sort of issue can never happen if M ≤ N."
In short: Every single result with thread higher than cpu total is "bugged" (understand not correct/accurate).
There will be a v2 of the bench (there are several ways to fix this).
Now the idea was to delete the old ranking and only allow the v2 of the soft. But the author hasn't made the v2 yet so what we can do in the meantime is freeze and clean the current ranking, allowing only subs with default thread settings in the future the time v2 is out. When v2 is out since results will not be affected (score with v1 8t = score with v2 8t = score with v2 64t), they can be in the same ranking. V2 will be mandatory.