It's a bit of a mash up, isn't it? From experience, Jason is great to work with but regardless of WireGuard being FOSS he does like to keep an arm around his 'baby', even in other projects. He expressed similar frustration with Cloudflare when they eventually branched off and created boringtun. As for Netgate, Jim seems a very strong headed character and the direction of the project is raising questions atm. They're talking about making pfSense+ available for free to the community across any hardware 'soon', and they say CE will remain but will be slower to update. They're selling that as 'LTS' and 'battle tested', but with TNSR and pfSense+ to handle it may just as easily turn into the 'neglected' version instead. Time will tell.
It's a shame WireGuard's kernel module didn't make it for FreeBSD 13, but hopefully Jason's polished version will hit 13.1 as projected. If that man can do nothing else, he can certainly write polished and focused code. I'm happier to wait for 13.1 and have 'his' WireGuard than rush into 13-RELEASE without it...
If Netgate do close source on pfSense that'll be a shame, but the BSD license allows for it and it is what it is. There can be no complaints there, albeit it's a shame and leaves you to wonder and only able to blindly 'trust' what's going on under the hood. There's always plain ole FreeBSD if it goes that way, and that will certainly remain open. I'll stick to OpenBSD for now, which already has a good kernel implementation of WG. Hopefully Free catches up soon, and pfSense to follow. We have to remember that Netgate at least sponsored the work, and it may not have been done at all without that original impetus. TBF it sounds like Jason would have been willing to help get it written regardless, but we'll never know. I stopped following Free so closely when all the CoC nonsense crept in and they had a lot of politics rattling around. It's still one of the best optimised releases for networking though, I don't think there's any arguing that.