Ny way to avoid copying a user’s Terminal Server profile upon logoff/logon

Currently, we have a TS with all user profiles stored locally. We have a DR server, which is synced by robocopying the C:\Users folder and performing manual configuration on the other end to update the links to the profiles (for new users).

This is obviously cumbersome. What I want to do is configure the user account objects to point to the TS profiles on a share (the settings/files would then be replicated via AD and DFS). However, the issue is that several users have large application files (a few GB) under AppData\Local, and we want to avoid having them copy each time a user logs on or logs off (does TS/RDS do differential copies on logoff/logon?). I created a local share on the server so the server will point to itself, but this still triggers the copy. I've also thought about making C:\Users a share so the network path will completely overlap the actual files, but I haven't tried it yet, and something tells me that this is a bad idea.

What is the best way to implement this?

Edit: Another requirement is that AppData\Local must remain consistent across profiles, meaning that it should be the same in production and DR. Apparently, Folder Redirection only works with AppData\Roaming, so that isn't a complete solution. It seems that the majority of the size of these profiles is in AppData\Local, so that's the key to handling this.