I have my doubts that Brave would be the problem.
Brave itself is unlikely to be the problem.
The problem is that Chromium, on which Brave is based, ships with Hardware Acceleration enabled by default.
I just had this very conversation on AskUbuntu today. (I don't normally have time to visit that site these days.) The person insisted that it worked on other machines. So, I shared a link that pointed out that it didn't actually work on any machines and that Google wasn't interested in making it work.
It wasn't that it was working on those machines - it's that it wasn't causing any problems on those machines. There's a HUGE difference between those two things, which seemed to be lost on the person asking the question.
Anyhow, not only is it not working, it exists in the Linux version of the application. It works just fine in Windows, but Google had 'no plans' to make it work in Linux. So, not only does it not work but it's enabled by default. Not only is it enabled by default, it breaks some operating systems, 'causing everything up to and including full-system freezes.
So, no... No, Brave isn't the problem here. The base software they're using is the problem. They can't really be blamed for this.
That said, I did read that there might be experimental hardware acceleration available for Linux users that also use an AMD GPU. It'd still be in the experimental phase and likely causing as many problems as it 'fixes'.
There's literally no benefit to keeping it turned on and all sorts of potential benefits to turning it off. The whole situation is straight up flippin' moronic and the only party to blame is Google. If it's enabled and not breaking things, that's great. It's not actually helping anything, but at least it's not breaking anything.