Well, FreeBSD has different feature flag compatibility at different times and it depends if you are talking about RELEASE vs CURRENT vs STABLE as they can have different flag compatibility at different times in their development since ZFS is integrated into the kernel. I know FreeNAS likes to incorporate the newest ZFS code possible too when they do a release since that's the primary purpose of FreeNAS.
Before I posted though I created a pool with data on FreeNAS 9.3 and made sure that it imported and worked read/write on my Linux test box and indeed it did. Those other flags are not activated by default then or else it would complain of the incompatible features.
For example, large_blocks is something set at pool creation time and the FreeNAS GUI doesn't allow for setting this (so it gets set to default) which is still compatible with all the other implementations without the flag.
Also I'm not aware of creating filesystem_limits on FreeNAS GUI or enabling multi_vdev_crash_dump (not sure why a FreeNAS user would ever use this as it's for debugging pools) which are the only other flags not in Linux at the moment so you shouldn't be able to create or get a pool that's incompatible with Linux from FreeNAS unless you use the CLI which is not recommended usage.
So yes I overlooked the actual absolute flag support between the operating systems, but I was sure to test the actual default pool support which for practicality in the case of the OP is what he seemed to be concerned with.
Also FWIW large_blocks and filesystem_limits are already ported and you can merge and build it yourself if you really want/need the support now. The pulls from Illumos for the latest features have been speedy from what I have been seeing and don't lag over BSD pulls by more than a couple days or week or two at the most.
https://github.com/zfsonlinux/zfs/pull/2865
All of the flags you listed from your FreeNAS output will be available in the ZoL release version 0.6.4 which is the next stable release version pretty soon.