The search has to "hit" one copy of every shard at least once -- it clearly needs to check the timestamp range to know whether to skip that shard or not. But that's all it does if the shard doesn't match, so it's very quick.
IIRC this behaviour is reflected in the profile API output - you shouldn't see profiler entries for the skipped shards since there's basically nothing to profile.