RT expires traffic when the last valid position timestamp is 60 seconds old. It is up to the client applications to deal with any logic that would expire them sooner, or stops painting them when the positions no longer update. If RT stops transmitting traffic that is no longer updating too soon, there's a chance much traffic in areas of sub-ideal coverage disappears prematurely, because often just one or two position updates (10 - 20s) are missing, then the traffic is back as another receiver picks up or they were just passing through a blind spot for the receiver that's feeding the data. All client applications I'm aware of interpolate the positions to provide smooth motion, and thus buffer 30s or longer before starting to paint traffic. There's only so much logic that can be handled on the RT servers I'm afraid.
Also, something RT will never do is send interpolated or artificial position data. Every position data point you get is real, was sent by the aircraft, and is authentic. Note this is NOT the case for altitude, V/S, speed, track, callsign - those might just be repeats of already buffered data. This is because of how the feeder networks work, as well as due to some information not being transmitted in every data frame.