honnestly, i kinda registred just to call on these statements.
. TrueNAS is a server-oriented OS and as such, WiFi isn't ever a thing for servers, AND 300kb will never be exceeded in any personal computer.
i do agree with you that running any type of server on a wifi connection is less than desireble.... but
let me explain: as of january 23 (only fair to keep it within time this remark has been posted),
aproximately 40% of all SOHO (meaning self employed, home office users) in western europe (NL, BE, DE, UK) either uses wifi mainly or exclusively in offices with more than 4 and less than 20 devices connected to their networks.
on avarage about 85% of all ISP's with a B2B internet connection provide SOHO routers that have upto 4 1gbit ethernet ports and/or upto 1 multi (usually 2,5) gbit ports.
so provided your office is small enought in might actually be beneficial to have direct access via wifi. especially given the fact that for example wifi 6e will be able to out pace (or at least come verry close to) wired gbit ports...
and yes the way that most aplienced provided network connectivity to for example vms or docker containers is via an ethernet hack that lets the network think you are a non-switching-hub, instead of just a client. sadly enought simular features are not part of the wifi standard, and it either supports a client mode or an accesspoint mode but not a hybrid mode (those things that do wifi mesh for example all have to do software switching)... this usually means a rather large burdon on your cpu.
however, there is a quite simpel solution to this problem, that would allow connection via wifi AND being able to keep full functionality quite easy.
1. setup vpn with as low overhead as you can, use low spec encryption, or encryprion types that your system has hardware ofloading for). one such example may be wireguard.
2. make sure that you vpn terminates on your lan network.
3. set your wifi connection on your nas, to default rout over your vpn solution and configure this virtual adaptor also for your vms and dockers.
4. enjoy.
an alternative sulution would be to have a reverse proxy running on this wifi and having natted or host-only ports on your internal (in server) network.
as you say, you can also use a wireless bridge, which if you are lucky, is dumb enought to actually transfer all packages to its lan port so that your nas can pick them up, however the main drawback of this is that most (if not all) of sutch devices have verry limited hardware and may well drop many many packets if put to any kind of load.
no remains the question if wifi would negativly affect any of the inplace systems, configurations or management tools currently in use,
as adding relevant drivers to the kernel and installed stuf like wpad might not be verry complicated, but doing so without f*ckin up the rest of the system may not be so trivial.
if anyone cares to help provide some technical backstory i think that a comunity supported work-around might be do-able.