Classification to understand date like this dd.mm.yyyy or mm.dd.yyyy

I have a suggestion to do classification of dates before giving output to user, for the what we can do is we can take a list of dates as input and understand the actual pattern and then maintain the pattern for the code.
Or even someone else can suggest better solutions regarding this.
I even have one more idea in my mind that we can create a compiler function just like we had in urllib or sessions in requests. This compiler will be specified the patter of date found.
Though this feature will be used by less people but it is very important to have.

Also please let me know if this feature are already implemented by which I'll be able to leverage those features and if not yet the please guide me I can contribute as well.

Motivation-
As I always talk to my seniors at work they always suggest me not to use dateparser because by they past experiences they have faced some issues while using dateparser. Issues were like sometimes dateparser used to give mixed pattern of outputs like sometimes it used to give dd.mm.yyyy and sometimes mm.dd.yyyy .

No files, tests, or entry points are named. Start by reviewing the existing date parsing behavior and how output formats are selected, then define the expected handling for ambiguous dd.mm.yyyy and mm.dd.yyyy inputs before proposing tests and an implementation scope.