Yes, it's set to "Fastest possible, but maintain chipset timing".
I agree about the FPU, but I don't believe in this case it makes a difference, as I'm not running anything that might use the FPU, and the dhrystones test being used as a benchmark is an integer test. I can switch off the FPU and retest but I doubt it will have much if any effect.
It is very strange that WinUAE is so slow and that JIT does not work :-( I wonder if I should submit a bug report to the new programmer of WinUAE, he will hopefully be more inclined to act than the previous programmer (BK). I've had this same problem with several versions of WinUAE and on two different computers.