One additional thing worth calling out: Inactive (long-term) is usually best thought of as an archive state, not only a sync control.
SailPoint will still do a final attribute sync when the identity transitions into that state, but after that the identity is generally outside the normal ongoing processing flow. The bigger impact is often operational reduced visibility in ISC for search, reporting, and follow-up handling.
So if the goal is to stop normal churn for those identities, enabling LCS on the identity profile makes sense. I’d just recommend piloting it first to confirm the transition behavior and make sure your team is okay with the visibility tradeoff and any exception handling later.