kubemark's proxy mode exists to test how kube-proxy affects the load on the apiserver, not how it affects the load on the node. There's no need to generate fake iptables commands, because that all happens entirely independently of the api watchers.
This way it inherits the OWNERS from pkg/proxy which makes it easier for sig-network to keep it in sync with changes made to internal proxy APIs.