That makes one aspect of it much easier, but then you need to enable routing on the Windows machine if you want the cameras to connect to anything beyond the NVR (eg: time servers, ftp server to push image snapshots, etc.).
You would also need to setup your "core" router (using that term loosely in this case) with a static route for 192.168.1.0/24 and 192.168.2.0/24 to point to the IP address of the Windows machine that is on the corporate/non-camera side.
Again, by no means is this impossible, but it is one of those scenarios where if you don't fully understand the network topology you're building you are very likely to turn every troubleshooting job into a huge nightmare. Additionally, I do not think there would be any practical gain to this. Most NIC's these days are 1Gbps, and few (if any) single-server NVRs are going to let you push more than ~500Mbps of data to disk, so your recording subsystem will max out before your network subsystem does.
If OP has a scenario where his ~96 cameras are going to saturate the NIC before the NVR software and HDDs, it makes sense to explore this. Otherwise, I'm not sure it adds enough benefit to outweigh the headaches.