The error message derives from this line in the provider code. The recently executed code checks the certificate details of the discovered filtered certificates at that point, and then compares among them for the "most recent". Not also that the error message is a typo and actually should say:
Error: most_recent filtering on different ACM certificate statuses is not supported
This is easier to understand. The ACM certificate documentation displays the information about the statuses. The problem you have is that your filters matched multiple certificates, and AWS is unable to further filter by "most recent" because the discovered certificates have different statuses. It would make sense that this would "suddenly stop working" because you could easily have one or more certificates that changed status in a day.
You would need to either modify your discovered certificates to have the same status, or modify your filters to only discover certificates with the same status prior to the "most recent" filtering.