You can observe a lot by looking at QV server performace logs for NPrinting User (using Governance Dashboard, or Server Performance app). Your bottleneck may be QlikView server (not NPrinting server)
Depending on template types used to build reports, objects used to build them you can manage NPrinting performance. (Example: if you have XLS template and you use pictures to put charts in it it is better to use XLS charts build form data exported from QV as it will significantly speed up report generation process)
It also depends on connection type - i always use qvp connection although it may be starting tasks slower in the long term it is more stable and does not kill the NPrinting box. Local connection will force your NPrinting Machine to be able to open at the same time as many QV instances with the biggest applications as many cores you have on NPrinting Engine Box and have enough memory to run it all in parallel. In long term it will run out of the memory anyway.
As you have multithreading in NPrinting 17 you are able to put a lot more stress on QV server and the issue can be on its side. With NPrinting 16 tasks were automatically joining queue and were stuck there until it was its turn to run.
I think you can monitor processes and its consumption when running NPrinitng reports on NPrinting box and see which process is killing its performance.
Down to your question though - I have not seen anything coming what would suggest that NPrinting performance will be monitored on the level you ask.