I've also tried the 'fix' that cesar.cintron posted about disabling sandbox protections. It's still slow as ever just as it was from the start of this update at the beginning of the year. I've just been left in the dark, hopeful that Adobe would fix the issue in a subsequent update, but that hasn't happened. I've still spent time scouring the web for info on this with no luck. It's now been 8 months since posting this question. I logged into the Acrobat Pro DC using my account credentials and Pro DC operated as expected.100% Agreed here. pdf file under each user had the expected result.

I then set one user to have Reader DC as default, and the other to use Acrobat Pro DC as default. Next I logged into the TS from a PC in two separate sessions with two user accounts and made the same menu and options checks. I checked my menus and my options for setting default apps both Reader DC and Acrobat DC were present. and clicked the upper right X when it asked me for my username. I logged in as Admin on the TS server itself, and opened Acrobat Reader DC. I entered install mode on the terminal server and installed Acrobat Reader DC, rebooted, re-entered install mode and installed the Acrobat Pro DC/Creative Clound bundle.

The only change I made from my failed attempts was to use the enterprise installer for Acrobat Reader DC. Adobe Creative Cloud v (bundled with the install package downloaded at the Teams site) Acrobat Pro DC v21.007.20099 (downloaded install package available at Adobe Admin Console for Teams) MS Windows Server 2016 with RDS installed.

Adob pro dc