No. You're going to be looking for the same thing you would using extended events. You'll have to capture any rpc_completed or sql_batch_completed events. You can try filtering for the DELETE keyword and the tables you're interested in, but filtering in trace is pretty horrible. You'd be better off capturing the events and then filtering the results after the fact. For example, set it up so that the trace outputs to a file. Have that file roll over every fifteen minutes. You then schedule something that reads the old file every fifteen minutes, looks for this particular sets of strings, then delete that file. It's not as good as extended events, but it will work.