I’m not sure it has to be so dramatic. I just tested the HA docker image on my laptop and with host_network: true it has absolutely no issues discovering devices, even with default SELinux settings that prevent DHCP snooping. Unless there is something significantly locked down on the OS side this should work on truenas with a simple app version bump.
The two potential issues I see are (1) at one point host networking did have issues (Home-assistant can't work with host-network enable) but this was in k8s land (2) there may still be some limitations compared to a full VM deploy (e.g. the [aiodhcpwatcher] Cannot watch for dhcp packets: [Errno 1] Operation not permitted issue) may prevent some things from working like bluetooth discovery, but most of core functionality would be unlocked regardless.
There is a pattern of “just VM it” being offered as a solution to any challenge but containers have come a long way in the past couple of years and I’ve had 0 issues running things like Frigate which previously were a hard no. The switch away from the complexity of k8s certainly helps this. I of course wish we were running on a modern OCI system like podman (most of the challenges with podman come from SELinux, but truenas isn’t even running that) but docker-compose is good enough.
Generally speaking the “app” version should work or it should not be offered.