Yep - directly after the last line (the root folder one).
It doesn't really matter exactly where you put it as long as you don't place it in some other remote's block (which is demarcated by [remotename] if you have several ).
I note you don't have an encryption remote.
If you are security sensitive - you might want to consider this?
There are very few drawbacks to using encryption on rclone from a technical perspective.
rclone will do so automatically. If you don't use the remote for several weeks it could expire, and you might need to re-authorize it via rclone config (edit remote and just keep all settings and do the re-auth step).
If a service-account is set up (authorization baked into a single file, used often on server-systems) it would never expire if that is important to you. But it's not like re-authing is difficult to do if needed.
Then whatever account (email address) you use in rclone must be a member of both teamdrives, and the user must at least have read permissions on the source and write/delete permissions on the destination. In teamdrives this is easy to set up (on google drive website), but ask if you run into any problems.
Happy to help 