What is wrong with tsclient?

We've been wrestling with tsclient using RemoteApp workspaces within Microsoft Remote Desktop  (MRD) for Mac for years when trying to interact with local files from within an app. It constantly gives access and permissions related errors, such as in cURL
== Info: Couldn't open file /tsclient/Home/Desktop/filename.pdf
== Info: Closing connection -1

We have no problems with RemoteApp workspaces running in Windows, or other Mac Remote Desktop apps such as Jump Desktop. Only Microsoft Remote Desktop, which we've been beta testers for years.

We note that in Windows the full folder path is provided, whereas in Jump Desktop the 'home' element in the //tsclient/home/ path is a truncation of the home directory name in Jump Desktop, so perhaps the use of 'home' is the problem? A web search indicates that we are not the only people with this problem.

The problems can occasionally be got around by manually pointing to a local folder or file, after which MRD will remember the path for the session, but the point of coding is to prevent users having to manually do this.

Come on Microsoft, please, please, please sort this out, or have you no pride that small independent developers can do what you cannot?