There are a few (mior) errors in the config shown. But I suggest you to go through this article, which explains different personalities of bridge entity in ROS. After understanding it, it becomes clear when bridge interface has to be member of certain VLAN (passing bridge switch-like entity) - it doesn’t have anything to do with L3HW offload at all.
One thing is that when you set some interface as bridge port, you should not use it elswehere as anchor for other config. In particular: ether1 is set as bridge port, yet you’re anchoring VLAN9 interface off it (this vlan interface should be anchored off bridge interface). Also beware of deault “native” VLAN … in MT it’s due to implicit of setting pvid=1 everywhere it might apply, but normal configuration export will not show it (in CLI, “export verbose” will show it though). Which is the reason for suggestions (expressed in numerous forum posts) to avoid using VID=1 explicitly.