A unique Reverse Proxy and Windows Clustered File Share Conundrum

Question

So, in the space that I work, we're not allowed to perform direct routing of specific services outside of a test network space, but we are allowed to have purpose limited reverse and forward proxy servers.

I'd been trying to find a means to make a couple key file share servers accessible via this method, and so far, the closest I'd come is using WebDAV for the file movements, but the 4GB down and 2GB up limitations make it less than practical due to some of the file packages that have to transit.

I found a second solution recently that makes use of nginx reverse proxy that works absolutely fine, so long as the file share is hosted on a single server file share.

The moment I try using the same solution with a file share that is a standard File Share role on a 2 node Windows cluster, it doesn't actually show the shares from the Cluster Role, just the node that's hosting the role.

My best guess is there's some kind of traffic transaction that I'm not accounting for with this method that is causing it to only show the cluster node vs the cluster role.

Any insights into the magic piece I'm missing about Windows File share cluster roles that's keeping this from working? Is there a multicast component that's not documented anywhere? (Google searches for Firewall ports for the Clustered File share roles don't yield any real practical information as to which piece I'm missing and the throw stuff at the wall till something sticks method isn't getting me anywhere on determining if this simply isn't possible due to a limitation of the mechanism or if there's some key piece I'm missing).

Would putting it behind a stand alone namespace DFS server get around this issue?