USERSTATE on channel join tells you if you are a mod or not. So you can check your permissions on room join, rather than after trying to run a delete command.
And, as you already found, replace TMI notice checks with helix 2xx or 4xx responses (that will also describe the issue in the body).
I would also argue this is better as you get a positive reply to your individual command.
Where as if you were to run two deletes in the same channel at the same time, you won’t know which one failed and which one succeeded, if one of the two attempts failed for whatever reason. (Sure ignoring IRCv3 nonce tag which you might not be using and I don’t remember if it works for this request as not documented)
Arguably the wrong token type since every 60 days you are going to have to manually provide your bot a brand new token. if you remember. (or wait for the first fail from a dead token).
You ought to be using the “regular” code flow that grants a token and refresh token. And then you have no manual steps (except in rare cases where the refresh token is invalid).
Sure you’ll need to renew the token with the refresh token every 4 hours. But you won’t need to manually provide a new token every 60 days when the implicit token dies.
I disagree I fully ported in about 3 hours from TMI commands to Helix on my bot for all features that needed swapping. But as I described I already had some HTTP calls in place for token checks and destination channel checks.