Chatgpt and DeepL are both better. They understand context much better and more likely use real expressions over literal translations.
I'm surprised you haven't run into problems with community verified translations. They're so predictably poor that I'd stop using GTranslate just to avoid that.
Like take a "Submit" button - it can mean anything from "send this request in" to "grovel in front of me" depending on context. Human localizers struggle with this, especially when the source files they're provided with do not have sufficient context (and they cannot see the GUI in-context) to infer meaning. Existing translation engines are worse.
And sometimes the lack of context is self-inflicted. My company just started evaluating translation services and as part of that process, we sent some of our strings to the candidate companies. Many of our strings are in Java properties files, which we've annotated with comments to give context.
Yesterday I got a request back from one of them: please convert the strings to a JSON file. Which is on some level the equivalent of, please strip out all the comments you added for our benefit.
Yes, I get that our strings will be fed into translation software. But still, we made the effort to give them context and they told us to get rid of it.