PLC cycle time = logic to execute + update outputs + update inputs + housekeeping + asynchronous comms.
Not necessarily in that order.
Asynchronous comms only get updated if their is time within the cycle, predetermined by timeslice. This is what your talking about above.
example: Lets say their is a 20% timeslice for comms in the overhead of these processors. (Usually you have control on the amount of timeslice in your processor)
Your Logic executes = 13mSec, Update Outputs = 1mSec, Update inputs = 1 mSec, therefore your comms has 3mSec to execute during the plc cycle. If it does not complete then it waits for the next timeslice. If you do not have enough timeslice set aside sometimes the comms will not get executed in a timely manner. If you have too much timeslice the plc cannot execute its program and real world outputs will be missed.
I know in AB contrologix if you have an event driven task it takes priority over any continuous plc task, in PLC5 or slc500 this is called an STI interupt, not sure what it is in siemans. If you have a periodic task, this is below event driven but above continuous. Your comms between processors or hosts is the lowest priority on a PLC.