Can Postgresql exploit "accidental" clustering in plans?
The planner is unaware of this type of clustering and so can't make decision based on it.
The two-step sampling method used by ANALYZE can generate skewed samples in this situation, possibly leading to a drastic underestimate of n_distinct.  It is hard to predict what the consequences of that might be without digging into the details of individual queries.