I would suggest to try the following:

1. For every stream you want the change set to go to, create a repository workspace based on the current state.
2. Search for the change set or select it on a work item
3. Right click and Accept the change into the repository workspace - note that the change set should be completed
4. Since the workspace is up to date with the stream there are no incoming changes and the like
5. Deliver to the stream
   

Problems that can occur are "Gaps" where the change set depends on other changes that are missing in the stream. RTC 5.x added more gap handling features.

You may also think of writing a pre-condition/follow-up action (depending on when you want your custom action to happen) on delivery of change-sets. But, this solution would work for future deliveries, NOT on the change-sets that have already been delivered.

Pasting a sample precondition to check change-sets BEFORE delivery:

public class TestPreconsition extends AbstractScmService implements IOperationAdvisor {
    @Override
    public void run(AdvisableOperation operation, IProcessConfigurationElement advisorConfiguration, IAdvisorInfoCollector collector, IProgressMonitor monitor) throws TeamRepositoryException {
        Object operationData = operation.getOperationData();
        DeliverOperationData data = (DeliverOperationData) operationData;
        List<IChangeSetHandle> changeSetHandles = data.getChangeSetHandles();
        //Here goes your custom actions on deliverable change-sets...
        }
    }      
}