Keep in mind that the code adjusts each nodes time. So you could be over 30 seconds out of time but still be issuing the correct timestamps to the network when you stake.
Yeah. This is why I'm not too worried about it. I mean occasionally there may be a leap second, (not sure if that would affect it). I think there was one a few days ago actually to get universal standard time back in being correct with the suns alignment.
The underlying security flaw really doesn't have anything to do with whether or not nodes are correctly in sync. The conversation about whats the correct time drift to use is more about security update than it is about having the perfect balance of time.
I think 15/30 should work well. How much longer do you guys want to delay this? I have already started coding it in, but can hold off any final commits until there is a clear consesus about the hashdrift, interval, and fork time.