Using criteria to restrict which PSRs can be used for a Save As

We currently allow some of our personnel to use existing PSRs as a template for new records they create. The downside of this is sometimes they copy sensitive information and attachments to the new PSR. I have confirmed via Oracle support that there's no way to limit the SaveAs privilege itself, preventing it from copying certain fields. Our second solution involves using criteria to control WHICH PSRs can be copied (for example, if certain fields are null, the user can copy the PSR). This worked until I tried to apply the restriction to fields on the Affected Items and Attachments