Local ExternalTrafficPolicy with local address question

I just recently became aware of this project and wanted to use it as it seemed to fit my use-case. The fact that it just works and finds the correct local eth interface is super valuable.

One thing I went on to try was to create a service with Local ExternalTrafficPolicy and quickly realized that it is not supported. While I understand the rationale, I would also like to understand if you would be interested in supporting that to some degree, by disabling some sort of safety flag. I explain.

Let's assume I have a service that is going to be exposed on the internet through a port forward rule WAN -> Internal IP. I'd have an Ingress service such as Traefik serving at that IP, which would be assigned to any of the nodes by PureLB. In this case, to retain the ability to see the original connection IP address, it's very important that I don't have the traffic coming to this service through kube-proxy, so I should be able to set ExternalTrafficPolicy to Local.

That's how I imagine this operation working, but unless PureLB supports that, it wouldn't work. I would like to be able to override the behavior of not letting local traffic be served directly and I know the downside is an uneven load-balancing, but even then it would be pretty minor IMHO, considering that Ingress itself would balance traffic (L7) to the downstream service anyway.

Is that a scenario that would make sense for such a change? If not, is there any alternative you would recommend instead?