I recommend using as little as date/day mechanics as you can get away with. Instead using a monotonic durations as much as you can [1].
If you continue to program with date/day mechanics you'll run into plenty of issues when users cross timezones or just set the time on their phone to a different one.
All the people pointing out the (genuine) problems with decimal time seem to be weirdly tolerant of the problems with our current system, which has much worse problems.
If you imagine the reverse situation, where society uses a decimal time, and some people are arguing we should switch to this system because despite all the things it makes worse and harder, it divides better and the numbers map somewhat (although imperfectly) to the actual time-of-day in various locales and (even less perfectly) to the kinds of things people might be doing at that time, everyone would think they were crazy.
If you want to prioritise ease of moving between the two systems, I'd suggest a normalised version of the new second. If you want to prioritise science, then something that makes a nice round number when giving the speed of light would be nice.
Either way the symbol for writing it should be different.
This is reasonable and not unsafe at all, particularly when it comes to timing things like exposure time with patients receiving radiation therapy.
However, we will be left wondering why treatment in the summer is more effective that treatment in the winter. Must be the nice weather.