What you describe looks like an intermediate layer between the application-level "print" (kdeprint in this case) and the spooler itself. IMO, this can be (and should be) implemented as a separate tool that can be fired from kdeprint through the pseudo-printer framework: just imagine a "Fineprint" printer bound to a fineprint-like tool that would do what you expect (collect, merge, rearrange, preprocess... print jobs). Unfortunately, I don't have the time neither the resources to implement such an addon.
What you describe looks like an intermediate layer between the application-level "print" (kdeprint in this case) and the spooler itself. IMO, this can be (and should be) implemented as a separate tool that can be fired from kdeprint through the pseudo-printer framework: just imagine a "Fineprint" printer bound to a fineprint-like tool that would do what you expect (collect, merge, rearrange, preprocess... print jobs). Unfortunately, I don't have the time neither the resources to implement such an addon.
Michael.