I am a bit confused here.
A "native vlan" is simply the vlan that carries the untagged traffic. If you are tagging it with the same tag as what the ports native vlan is configured for you are treating the "native vlan" like any other vlan. The client shouldn't know anything about the native vlan.
You can't currently send tagged vlan packets through neutron, at least you can't with OVS. See the relevant code here, OVS is stripping the vlan off the packet before tagging it its own way.
My guess is the linuxbridge plugin works the same way, but I am not positive on that.
What is your overall end goal here?