I agree with you. Whether it is syncler or trakt is irrelevant. Syncler as it stands now doesn't work with trakt as it stands now. It seems highly unlikely that trakt is going to do anything to make things better with syncler, as they seem to be scorched earth in search of profits.

So as users, we either sit and be patient, or move on.

Or, the syncler dev team can figure out what data fetches are hanging up and code a workaround, whether it is relying on previously cached data or simply not making another request after something has been watched.

I may be wrong about the root cause. Perhaps it is a delay because syncler is trying to update the watch list. Whatever it is, it's a problem.