Personally, my inclination is to keep it simple... recording to something else just adds a potential point of failure.
I record to my local (SATA) SSD (which has plenty of spare space to allow proper wear levelling), then I move my Recordings to an Archive drive when I'm done Recording (and auto-remuxing). And, my process is to actually wait until after my cloud sync backup makes a copy of the Recording, before moving the Recording... so just in case something goes wrong, I have a backup I could recover from offsite... which I've never needed...
For me, it is easy/quick enough, and only Recording once a week, so not so time consumptive as to bother automating. But using a simple ROBOCOPY or similar script to move a Recording would be super quick and easy if the time savings became material
As for your NAS... depends on you lower threshold throughput... as to whether it can Save video stream fast enough to not be an issue. A typical NAS device is MORE than capable of locally saving recording at sufficient write speed to not be a problem. The consideration is your PC, your PC's security software and related settings, other network traffic on your PC, LAN, LAN traffic, other NAS traffic, NAS settings, etc. There are LOTS of potential bottlenecks.. as long as your are aware and plan accordingly, you should be fine. Like WiFi, there are also plenty of circumstances when trying to sustain a video file write over LAN that can trip you up (and you won't see yourself approaching those 'obstacles'). It is totally doable to write Recording to NAS. but.. plenty can go wrong as well, if you aren't careful. For me, too much risk/hassle to bother with, with I have plenty of spare space on local SSD, and have no concern about overall TB written (TBW) on SSD itself