Multiple things here...
1. OTB, the requested state change from Promotion only occurs after the workflow process completes. If you use watermarking that is dynamic by state, printing can only be done after the promotion workflow, not during it. This may be ok if the printing jobs are just notifications but will be a problem if they need to be completed before the process ends. Not an issue if you don't publish and use dynamic watermarking (but why would anyone not use these?).
2. You can add a conditional in the workflow template after the user choice to route to printing that branches around print (skips it) if the affected objects do not include any Drawings (need to get code for this from others).
3. If the Task is tied to the Promotion Request, not the affected objects on it, then this will result in one task for each promotion request, regardless of the number of drawings on that request.
4. By the way, it's absurd that the default "Basic" lifecycle template includes Canceled (spelled wrong above); what real business would ever use Canceled? May want to remove this state. I don't see above a set state robot in the workflow template. May want one just in the branch used for printing (if it's helpful to know that the process is waiting for printing to get done). If it's just an open-ended notification, then no such need.