Why do we need to do masq for the local lb on the host?

Why does masq need to be performed when accessing the local type lb service on the host?

When I deleted the following rules, I found that directly accessing the local loadbalancer ip on the node can still be accessed.

like this:

iptables -t nat -D KUBE-EXT-5J2MEIPCD4GMETYI -m comment --comment "masquerade LOCAL traffic for kubernetes-check/lb-nginx external destinations" -m addrtype --src-type LOCAL -j KUBE-MARK-MASQ

Before deleting the rule, I can be sure that this rule will be hit when accessing
So I don’t quite understand what kind of scenario this special masq rule is designed for

I hope someone who knows can give a specific scenario to point out what problems will occur when masq is not executed.