Let\'s say I have a resource that can have two different behaviors when delete is called
Your idea is fine, but I think a custom request header would be a little more appropriate. Query parameters are better suited to, well, parameters.
A custom request header would look something like this:
DELETE /myresource X-Really-Delete: Yup