I use very large documents with my NPrinting. One is 12 GB in size. I will give you my opinion based on my experience which may or may not be considered best practice. We are still using ver 16, so if you are on 17, this may be different.
I think the frequency that you are updating your data can determine the answer to your question. We only update our data once a month, so we choose to have a static QVW file that we copy and use for Nprinting purposes only. If you update daily or more often, this might not be a practical step
This also enables us to use several schedules for printing. I can use the server and have it read its own QVW and I can also use a client or two to run schedules locally. This divides my load. We have several people that use NPrinting clients for development and just have the QVWs loaded on a local drive.
I would say the optimal best practice would probably be to read the QVW's directly from your QV server. You will have to do some experimenting and see what works best for your scenario.
Not sure I answered your question but hope I gave you some perspective.
I would look in your data governance dashboard and see how often your users are exporting data out to Excel. It should be pretty easy to put together a cost justification if you are saving the labor of the everyday tasks.
Perhaps you could justify starting with the SMB version and upgrading after proving cost ROI.
Check with your partner on pricing options.