Yes, this has been known for quite some time to affect a minority of systems negatively. That is why Garuda changed the default BTRFS quotas setting to disabled. We now leave it up to the user to decide if they want to enable BTRFS quotas on their system.
Even though this issue was found to affect only a small subset of Garuda users, it was felt that the best policy was to leave quotas disabled by default, (just to be prudent).
Totally makes sense. I only enabled it because I wanted to see the extra columns on the Subvolumes tab - but the cost is not worth it when there are other ways to garner subvolume disk usage metrics by other means.