In your specific case.

If there was a supported command that did what you're asking, it would have to be supported for everyone, from top DBAs that know the risk down to someone that looking at SQL for the first time. A supported "break my DB beyond recovery" statement is something I hope never appears in the product