Sorry, but you aren't thinking like a security professional here. Consider the case, e.g., where you create a domain, delete it and recreate it. An attacker monitoring the deletion can with impunity wipe out your data at a later date.
An attacker monitoring the deletion can with impunity wipe out your data at a later date.
Only within the next 15 minutes. Beyond that point, AWS will reject the request for having excess clock skew.
As for "wonderful heisenbugs" -- the AWS services return a clear "hey, your clock is broken" error, so it wouldn't be very hard to developers to figure out what was going on.