Unrelated, but I'm not sure it makes sense to translate the time zone names at all, since they're identifiers. Here's an example:

      time_zone: [África/Argel, África/Cairo, África/Casablanca, África/Harare, ...]

/faker/lib/locales/es-MX.yml:15

Each timezone has a name that uniquely identifies the timezone. Inexperienced users are not expected to select these names unaided. Distributors should provide documentation and/or a simple selection interface that explains each name via a map or via descriptive text like "Czech Republic" instead of the timezone name "Europe/Prague". If geolocation information is available, a selection interface can locate the user on a timezone map or prioritize names that are geographically close. For an example selection interface, see the tzselect program in the tz code. The Unicode Common Locale Data Repository contains data that may be useful for other selection interfaces; it maps timezone names like Europe/Prague to locale-dependent strings like "Prague", "Praha", "Прага", and "布拉格".

This quote from Theory and pragmatics of the tz code and data - Timezone identifiers hints that the timezone names can be mapped to translations, but the unique identifier aspect gets lost if the timezone's name itself is translated.