Devolutions Server - load balance and Windows Authentication via RDM

I am having issues deploying Devolutions Server as a load-balanced solution (I have the enterprise license.) Here's what I have done so far:

DVS01A .mydomain.com- Node 1 - DPS is installed and configured for Windows Authentication
DVS01B .mydomain.com- Node 2 - DPS is installed and configured for Windows Authentication
DVS01.mydomain.com - L4 or L7 load balancer

DVS01A and DVS01B web interface work with Windows credentials
DVS01A RDM connections work if I set the datasource to the DVS01A.mydomain.com and check Window authentication
DVS01B RDM connections work if I set the datasource to the DVS01B.mydomain.com and check Window authentication
DVS01 web interface work with Windows credentials
DVS01 RDM connections work if I set the datasource to the DVS01.mydomain.com if I UNCHECK Windows authentication and supply windows credentials manually
Bypassing the load balancer using hosts file has the same symptoms

What I'd like is to be able to use the current Windows credentials to connect to DPS from RDM without having to type the password (they already have to supply MFA on launch.)

By changing the namespace from a server to a shared namespace, I understandably break Kerberos. I would expect it to fail back to NTLMv2, but that doesn't seem to be the case. Regardless, when I try to create a namespace via setspn and assign it to the SVC account that the DPS App pool is running as, I am still not able to login. What's interesting is when I enable Kerberos debugging, I can see that I am successfully logging in via Kerberos, but I am still getting 401 errors like this:
2021-10-13 02:06:41 10.x.x.x POST /dps/api/loginWindows/partial - 443 - 10.y.y.y RDM/2021.2.16.0+(Windows) - 401 0 0 33

Do you know of a way to get Windows Authentication in RDM to work with a load-balanced DPS name?

Thanks,
Paul