Best practice: look for the date/time format string in the WP translations and use that in Crowdin.
I understand and think e are saying the same thing then - the issue is in the translation. With some knowledge when translating the string it can be fixed by the locale leads.
basically in WP the locale leads have aligned all date formats and everyone conforms to the locale standard for new strings, what I think happened is that localizers simply forgot to align the destination to the rest of the locale.