Recording and streaming requires 2X the work. UNLESS you use the same settings for Recording as using for streaming (ie creating one video stream, and recording that). I for example, don't do that as my stream provider doesn't accept input at as higher resolution as is my camera/environment. So I stream at a lower resolution, and record at native (higher) resolution. And that is extra workload for CPU and NVENC
The whole point of using NVENC is to offload some of the computationally demanding real-time video encoding to dedicated purpose designed circuits on GPU, thereby reducing workload on CPU. So, by definition for a given workload, if you are using NVENC, then CPU workload will be lower than not using NVENC. Now, with that said, once you've off-loaded certain workload to NVENC, the CPU is free to do other stuff...
- some don't have enough CPU to both, say gameplay, and use OBS to stream/record
- Others, once they have OBS working with their other workloads, start getting fancier by adding CPU workloads by using other OBS filters and effects (like Audio filters, or chromakeying, or any number of other options, or plug-ins which use CPU). And some items use more CPU than others.
What we don't have, in OBS Stats, is a way to identifying BOTH OBS main process, and any associated processes (like NDI, or plugins, etc) and combine that to see an overall OBS resource impact on PC. For example, on my system, showing OBS stats, eh OBS CPU indicator in 1-2%. Though technically accurate, it is also meaningless to me as that amount is NOT reflective of the overall system CPU impact of OBS and associated components (which will vary per system, not something simple to program to display)
Hopefully, I answered you question. If not please be clearer in your question