Fix tuning timing results

[BrianHarrisonAMD]

Tuning timing results for CK solvers were not timing the same as other solvers which lead to differences in results.
This is due to timing based off a scoped start/stop event which includes the CPU timing, and also includes the other start/stop events synchronizing which gives improper timing results (leading to higher overall runtime compared to other solvers).

There is also an additional issue where only the fastest solver within a family of solvers would record it's timing values.
The combination of these issues made it so the MISA solvers were being selected, and hiding the other potential CK solvers.