Ok, gyus. I just had a call with the support and was told the following:
The support is aware of us having problems of hitting the limit, they were contacted and had the same problem reported several times.
They’re quite sure the limit has something to do with the requests send by RClone. He told me the backend has somehow changed the last time and that the limit is enforced because all RClone users use the same requests.
I told him that I also tried my own client id and this made no difference, then he told me he is quite sure it has something to do with the software I’m using and suggested me to try to use my own client id together with own software with exponential backoff implemented (at the moment I don’t have time for that). If I still got the error with my own application, I should contact him again and he will forward everything to the drive team and they’ll have a look at it.
The last thing he suggested me is to motivate the RClone developer(s) to get in contact with the Google support to see what’s wrong about the RClone software together with Google drive.
As far as I see it, this is our best chance for fast results.
@ncw, it would very kind if you could take some time to contact the Google support and at least give it a try.