I just did a moment's research on this and it frankly sounds like a nightmare. From the Wikipedia page on Leap seconds (see particularly the bolded bit at the end – emphasis mine):

The leap second was introduced in 1972. Since then, 27 leap seconds have been added to UTC, with the most recent occurring on December 31, 2016.[1] All have so far been positive leap seconds, adding a second to a UTC day; while it is possible for a negative leap second to be needed, this has not happened yet.

Because the Earth's rotational speed varies in response to climatic and geological events,[2] UTC leap seconds are irregularly spaced and unpredictable. Insertion of each UTC leap second is usually decided about six months in advance by the International Earth Rotation and Reference Systems Service (IERS), to ensure that the difference between the UTC and UT1 readings will never exceed 0.9 seconds.[3][4]

This practice has proven disruptive, particularly in the twenty-first century and especially in services that depend on precise timestamping or time-critical process control. And since not all computers are adjusted by leap-second, they will display times differing from those that have been adjusted.[5] After many years of discussions by different standards bodies, in November 2022, at the 27th General Conference on Weights and Measures, it was decided to abandon the leap second by or before 2035.[6][7]

So the best we could do would seem to be a hard-coded list of past times when a leap second was introduced. But even then, I can only begin to envision the mess this would cause. For example, any kind of arithmetic on times would become extraordinarily complex in the presence of leap seconds. (e.g., connected to the other recent NASA issue, modulo on times would much more often need to be left undefined.)

So, unless there is a strong need for this, this does seem like something best to just document as unhandled.