Actually this is a complete new question, isn't it? 😉 There are approaches you can use. First I suggest you assign the traveler to a label with a new name like resource at the token in the Event-Triggered Source. Then you need not duplicate the processes anymore.

You need a condition up on the process knows, which transporter stops. I would add a label at the transporter object called like shouldStop but any other name fits, too.
The process flow needs a Decision Activity to test the condition to delay or not. The condition reads the label at the transporter and compares it with the value that the condition becomes true or false. On true for example the delay occures, on false not.
