...
Cool beans kano. looking at the time pool 10 detected a new block "[2017-12-15 18:31:22.953] Stratum from pool 10 detected new block at height 499476" with the time that slush pool finised the block 499476 and got it relayed in was at 18:31:17 so its looking like it only tool a few millseconds less then 6 seconds for the pool to be geting cracking on new work. from the time slush got the block before that relayed in. Thats seem pretty darn quick. but if I happen to be looking at the right moments again and notice any big discrepancies in the time displayed on the top of the kanopool page I will try to take note of how much the time is off if I happen to notice again.
No, 6 seconds is WAY too slow.
But I suspect you are misreading that time.
The time in the block is not when it was found.
Block 499476 has a date stamp of "2017-12-15 18:31:17" which is the (somewhat random) time put in the block header, not the time the block was found, and certainly not the time that pool processed the block.
If it was, then that would mean that slush is slow to distribute their blocks.
All our node's bitcoinds processed the block during the second of "2017-12-15 18:31:22"