Answer
No — the reporting framework treats a print job containing multiple selected records as a single job, and a Report Rule's behavior (such as the 'no multi' setting) applies uniformly to the whole job rather than differently per record inside it. If genuinely different handling per order is required, the practical workaround is generating a separate print job per order in the first place (if the module you're printing from supports doing that), since Report Rules can then be defined per individual print job rather than needing to discriminate between records bundled into one combined job.