RDP access to a Windows machine without disabling access to it’s PC/SC devices

I want to remotely control thru Remote Desktop Connection running on (Windows 10) machine A another (Windows 10) machine B configured for Smart Card personalization. Machine B runs a GUI application that access the PC/SC reader physically connected thru USB on machine B.

Problem is that within a Remote Desktop Connection, the PC/SC reader is no longer seen by the application, even though I login with the same user/password, with that user an administrator of machine B. Same if I start a new session, or use an existing one opened locally on machine B.

The Smard Card reader is still visible thru Remote Desktop in Device Manager running on machine B. Experiments shows that the application running on machine B and attempting to use the PC/SC reader fails, or not, depending of when the remote connection is established:

Establishing the remote connection after SCardConnect works for testing, but negates the purpose of using Remote Desktop Connection in the first place.

Several Generative Pre-trained Transformers gave suggestions that did not change anything for me:

• On machine B, in gpedit.msc, Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection, activating Do not allow smart card device redirection, then gpupdate /force or/and restart machine B
• On machine B, using RegEdit to set (or in my case confirm the previous step has set)

  [HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services]
  "fEnableSmartCard"=dword:00000000
  

• On machine A, invoking Remote Desktop Connection with mstsc /admin

Any idea to prevent the Remote Desktop client on machine B from interfering with PC/SC? I don’t know if this is deliberate for security reasons, or a side effect of the gear that would allow login on machine B using a Smart Card on machine A (which I don’t need).