it's a whole lot easier for you to just include the aforementioned --exclude flag in your script that you are likely saving anyway to run each time, than it is for the team to stitch this in at the code level
It is not about easiness, it is about collaboration, working with a team and to avoid dumb files in the tree. You probably use a .gitignore in a git repository
What script ? At that point, the most relevant solution is to alias rclone
There is an issue to put flags into the config file as configuration profiles. It isn't implemented yet but it is on the list!
You can also set environment variables which may be interesting RCLONE_INCLUDE_FROM and you mentioned .gitignore - rclone supports --exclude-if-present which might be useful.
I assume you don't type out the rclone command each time you sync. don't you have a premade script you keep handy so you can just schedule it or execute it at will?
i did the same thing for a while. but i very quickly realized i was spending a LOT of time typing scripts into that little black window. now i keep a OneNote window open and just copy/paste whichever script i need for recurring manual syncs, and the every-day ones i just have windows task scheduler run a .bat file. but i guess we have to keep around 2 million files synced that are distributed on 4 servers, so a little automation goes a long ways.