Failing in 32 & 64 bit versions 2023.001.20093 and 2023.001.10143 on Windows Server 2019 Remote Desktop Session Host (untested on other environments)

Brief: Users with print rights assigned via a group, not direct permissions (see caveat below), quick print will open Reader but does not send a job to the printer (only Acrobat Reader, file types to other apps quick print fine)

Extensive details (I have procmon captures too)

Normal printing works fine. If they open a file with any application and file > print or CTRL+P etc. it prints successfully. Quick print opens Acrobat Reader, but in non-working scenarios the file doesn't ever show up visible but the recent says it was opened just now (working scenarios you see it open for a short period)

Environment:
- Windows Server 2019 Remote Desktop Session Host server with printers installed locally
- Everyone group removed from printer and replaced by group user is a member of with print rights
Note: this is a requirement, every printer cannot be visible/usable by all users.
- Adobe Acrobat Reader DC (latest patches) is default for PDFs
- Outlook Quick Print, right click > Print, or a custom app trying to quick print PDFs opens Acrobat Reader but does not print

Working Scenarios:
- Printer has the LOCAL groups Interactive, Users, or everyone added with read permissions and print (read alone is not enough)
- Printer has the direct Active directory user added with read permissions and print (read alone is not enough)

Failed Troubleshooting Tests
So far I have found no other working scenarios. I have tried the below, and probably much more, with no success.
- User with nested membership to Active Directory Domain Local security group with read/print
- User with direct membership to Active Directory Domain Local security group with read/print
- User with nested membership to Active Directory Global security group with read/print
- User with direct membership to Active Directory Global security group with read/print
- Assuming maybe a background item needed permissions, I tested with the following built-in local security principals with permissions ranging from read/print to all permissions (local): Authenticated users, LOCAL SERVICE, NETWORK, NETWORK SERVICE, SERVICE, SYSTEM
- Active Directory computer account with read/print, manage docs, and manage printer

Important notes:
- Acrobat Reader must be closed between tests or after a successful test, if you remove the rights that made it successful, it will continue to work. However, after closing and re-opening it will fail again.
- Best I can tell, restarting the print spooler doesn't matter. There was a period where I was restarting it regularly.

• Windows Server 2012 R2 Remote desktop session host, locally installed printers with the same version of Acrobat Reader DC works with non-default permissions. Same with Windows 10 network printing to a server 2016 print server (non-default permissions).

Extra info + description of attachments:
The larger image is a side by side of procmon during a successful test, user is directly there with print permissions, (on the right) and a failed attempt, user has print access via a group (on th left). The Spooler-Between.png is the exact same in both scenarios and occurs JUST before the other image deviates from one another. Best I can tell it's not helpful.

The default printer has been set via the legacy way, modern way, and set to let Windows manage (acrobat closed, user logged off and back on) and the issue persists.