Even if it is a problem, is there some way of removing them?
FWIW I would try running ProcMon to see if it would expose whatever the implementation is for that, e.g. whether registry or file access. That would refine your symptom description and help give you more information to help you devise a feasible workaround.
Alternatively since ProcMon seems to be less useful than it once was, whether due to optimization or evasion, you may have to try using some other traces. E.g. this command pipeline gives a list
netsh trace show providers | sort /+40 | clip
Then Paste that into a Notepad window and save it for future finds. ; )
For example
C:\Users\VMUSER\documents>findstr /i "remo rdp" "Netsh Trace Providers Sorted.txt"
{20C46239-D059-4214-A11E-7D6769CBE020} Microsoft-Windows-Remote-FileSystem-Log
{51734B23-5B7E-4892-BA8E-45BC110B735C} Microsoft-Windows-Remote-FileSystem-Monitor
{1B8B402D-78DC-46FB-BF71-46E64AEDF165} Microsoft-Windows-RemoteApp and Desktop Connections
{5B0A651A-8807-45CC-9656-7579815B6AF0} Microsoft-Windows-RemoteAssistance
{1139C61B-B549-4251-8ED3-27250A1EDEC8} Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
{3903D5B9-988D-4C31-9CCD-4022F96703F0} Microsoft-Windows-RemoteDesktopServices-RemoteFX-Synth3dvsc
{741C6BE3-F74B-4E4D-88E7-5CE3A35FAEB3} Microsoft-Windows-RemoteDesktopServices-RemoteFX-VM-User-Mode-Transport
{F1394DE0-32C7-4A76-A6DE-B245E48F4615} Microsoft-Windows-RemoteDesktopServices-SessionServices
{1A870028-F191-4699-8473-6FCD299EAB77} Microsoft-Windows-Remotefs-Rdbss
{127E0DC5-E13B-4935-985E-78FD508B1D80} Microsoft-Windows-TerminalServices-RdpSoundDriver
{C76BAA63-AE81-421C-B425-340B4B24157F} Microsoft-Windows-TerminalServices-RemoteConnectionManager
{54FFD262-99FE-4576-96E7-1ADB500370DC} Microsoft-Windows-Wordpad
{D4199645-41BE-4FD5-9D71-A612C508FDC6} RdpCore Api Trace
{D4199645-41BE-4FD5-9D71-A612C508FDC7} RDPEncComTrace
{5A966D1C-6B48-11DA-8BDE-F66BAD1E3F3A} TS Rdp Sound End Point Trace
{04C6E16D-B99F-4A3A-9B3E-B8325BBC781E} Windows Remote Management Trace
Good luck