You don't seem to have been far off here actually - since you already tried to use a separate cache for each. I think the main problem for the error was that since you never specified a manual location for the cache - the default location was used for both, and that probably made their database files overlap - confusing rclone into effectively treating it as one cache.
Here is a modified template with a few minor fixes and some suggestions. I have not tested this config so I may have made minor mistakes or syntax errors. I'll help you solve them if needed.
I have bolded the important bits and stuff that may require your attention or understanding.
Remove my <---- comments before use obviously. #### comments are ok to use in the config permanently as you please.
########### Standalone Gdrive ##########
[Gdrive]
type = drive
scope = drive
token = {"access_token":"ya29.ImGbB7ZOPzMoErFov3_MXQhUpaL1ryFcQsPB8EbL_2EmVenrDyGeU1XJc4Bwd8pxCN4q3zwCMemdKlOnW21uqOTKP7OD-lgz3NbbWQoxz","token_type":"Bearer","refresh_token":"1/goP_nSubc-vZk3jTFjDGmvKCtRlfVwGAmDjj8Vb5iCEa","expiry":"2019-10-10T04:34:58.912721994+02:00"}
client_secret = secret
client_id = client_id
chunk_size = 64M <--------- Not required but better uploading performance for some more RAM use
server_side_across_configs = true <--- enables server-side copying when possible
[GdriveCache]
type = cache
remote = Gdrive: <--- simplest possible for illustration, modify if desired (cache whole drive)
plex_url = https://plex.plexserver.com
plex_username = email@gmail.com
plex_password = password
chunk_size = 64M
info_age = 2d
chunk_total_size = 32G
chunk_path = $HOME/.cache/rclone/cache-backend/Gdrive <--- manual location for cache files
[GdriveCacheCrypt]
type = crypt
remote = GdriveCache:/Encrypted <--- for illustration, here assuming you want your encrypted files in a seperate fodler. If you ONLY are going to use encrypted files it can just be GdriveCache:
filename_encryption = standard
directory_name_encryption = true
password = password
password2 = password2
######### Standalone Teamdrive #########
[TD1]
type = drive
client_id = client_id
client_secret = secret
scope = drive
token = {"access_token":"ya29.ImCbB-aHpIwxghAng7Rh0392GziWGnmCPN1tc_CSKyRleuPeudtN_M4Pna9DR6HlF5YQUGlKACe-Bkwt-2U9C8SPYC1wCzC0","token_type":"Bearer","refresh_token":"1//03nQsrf6IfRAAGAMSNwF-L9IruGmnC4B06nO4pm9ECgSwrHYdiU1zN47SYqxHs-YkghyiSmXNiJgGIk","expiry":"2019-10-10T04:38:58.322624269+02:00"}
team_drive = team_drive
chunk_size = 64M
server_side_across_configs = true
[TD1Cache]
type = cache
remote = TD1:
plex_url = https://plex.plexserver.com
plex_username = email@gmail.com
plex_password = password
chunk_size = 10M
info_age = 1d
chunk_total_size = 10G
chunk_path = $HOME/.cache/rclone/cache-backend/TD1
[TD1CacheCrypt]
type = crypt
remote = TD1Cache:/Encrypted
filename_encryption = standard
directory_name_encryption = true
password = password
password2 = password2
This is the simple setup with separate caches. You can then rclone union them together, or use the (currently more well featured) mergerFS availiable in Linux. Union is likely to get updated soon to be brought more in line with mergerFS's most important functionality, but not quite yet. Each solution does have some benefits and caveats I can elaborate on if you ask for it.
I could propose a shared-cache alternative instead, but aside from it being easier to administrate it won't have much benefit unless you are keeping a significant amount of the same data on both drives. Let me know if you want more info on that.
As far as server-side copying goes, I have enabled the required line in the config for you. This should enable you to simply copy files/folders from one remote to another without it going through your PC / bandwidth. I have personally only used it on teamdrive-to-teamdrive, but since personal drives are based on the exact same underlying system I expect it will work fine. The reason this option is not enabled by default is it can't be guaranteed to work between all setups and configs, but at worst - it shouldn't do anything bad or destructive, so you should at least test it. you use server-side copy/move/sync via the normal commands and rclone will try to do it server-side if possible when this is enabled (if --verbose logging is used it should note these transfers as being server-side at the end of the line).
rclone move Gdrive:/SourceFolder TD1:/DestinationFolder -P --fast-list
This example for simplicity is not referencing Crypt or Cache.
You can transfer encrypted files just fine, but if you tried to decrypt them, transfer and then re-encrypt them then this would force them to go via your PC (as that's where the encryption happens). This can add some complications you need to think about. It would be easy to do...
rclone sync Gdrive:/Encrypted TD1:/Encrypted
But referencing something spesific inside the encrypted structure can be tricky as you'd need to use it's encrypted path and name to do that, and half the point of encryption is to obscure
Encrypting the contents of files but not the names is an option though ... or filenames but not folder names, which is reasonable security compromise if you want to be able to do this spesific thing more easily.
I will stop my rambling here and leave you to ask followup questions rather than cover every possible eventuality