Are you referring to a stale channel state that's been published that is now outside of the CSV timelock period? Yes, competing for confirmation in a block in that case would be paramount.

But prior to that you'd still have plenty of time (days) to penalize a stale force close attempt due to the to_self_delay that you set for the channel when you opened it. A time-locked transaction wouldn't validate on any node prior to that.