I did something similar in 2016 with (5) new Falcon F16v2(s) ... and it worked great.
One caveat -- if you run the F16v2 controller test -- the RGBW colors on the pixelnet out channels wasn't always right. So it turns out that its still fine, and they won't do that when controllers from xlights or FPP.
Because each F16 basically includes the output capability of (1) DLA Etherdongle, only potentially more configurable, the only catch is you have to configure all 4 serial outs to be pixelnet, and the starting channel numbers for each, but remember only the first output port is then used (and all four PN universes go out on that as PN U1,2,3,4). I believe if you ONLY configured port1 to be a single pixelnet universe, then the other 3 jacks are configurable to DMX, Renard, etc. You might need to change your dla hub PN jumper to U#1 but other than that it should work fine.
I had two of my F16v2 configured with all 4 serial outputs of pixelnet going to (1) DLA active hub each. Then each of those dla active hubs going the DLA SSC(s) -- one per house (roof elements). I only needed to do one pixelnet out, but I treated it like an etherdongle, just so I wouldn't get confused, so I kept my hubs jumpered the same as they had been when I was using 2 etherdongles.
I don't recall but I also only "THINK" you can configure each of pixelnet out to any range you want (as long as its a subset of E1.31 range of universes you are receiving), but in my case I just configured all 4 pixelnet out universes in contiguous PN universe ranges ... and treated it like an etherdongle doing the first 16k as described above, since I had no need for DMX or RENARD on the other 3 RJ45 output ports.
Side note: I would advise using the Falcon usc ssc firmware on any DLA SSC(s) .. and use the Falcon uSC/SSC Programmer instead of the DLA SS Utility. THis way, if you need to reprogram the SSC(s), you could basically unplug the appropriate F16v2 from the DLA hub ... and plug in a DLA Etherdongle or DLA USB DMX dongle flashed with pixelnet (what I used) and re-program in the field that way, if needed. Just don't check "program all SSC on hub" when programming in the field like that. I haven't done it yet. I programmed each SSC v4 with the usc/ssc Falcon Programmer and checked the "program all SSC on hub" ... but only had ONE SSC connected at a time, and this allows you to assign the initial start channel and a description for each SSC. Thats very nice.
I also think you might be wise to have a second f16v3 if you can, just because once you have ONE, your going to be wanting that second !!!
I would also advice you to get at least 1 of the 16ch expansion boards because you double capacity for so cheap, its almost foolish not to. I ended up using my expansion(s) this year and had not planned on it ... so was happy I had 2 expansions to use.