I tested you script and executed it multiple times, this is the result:
2024-12-12 17:10:00.023 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:00.021+01:00[SYSTEM] Java: 1734019800023
2024-12-12 17:10:11.085 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:11.083+01:00[SYSTEM] Java: 1734019811084
2024-12-12 17:10:12.714 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:12.713+01:00[SYSTEM] Java: 1734019812714
2024-12-12 17:10:16.171 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:16.170+01:00[SYSTEM] Java: 1734019816171
2024-12-12 17:10:19.061 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:19.060+01:00[SYSTEM] Java: 1734019819061
2024-12-12 17:10:41.203 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:38.287+01:00[SYSTEM] Java: 1734019841203
2024-12-12 17:10:45.395 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:10:42.480+01:00[SYSTEM] Java: 1734019845395
2024-12-12 17:11:13.854 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:11:08.006+01:00[SYSTEM] Java: 1734019873854
2024-12-12 17:11:15.560 [INFO ] [nhab.automation.script.ui.5e15a0112c] - JODA: 2024-12-12T17:11:09.712+01:00[SYSTEM] Java: 1734019875559
As you can see the JODA time starts to drift away. I converted the last java timestamp into a readable form, it equals the log time (17:11:15).
Of course the multiple layers (Windows, WSL, Docker, openHAB) may be the source of the problem. But the basic setup worked fine for a long time, the problems came up after switching to a new host. So this might be related to other hardware or a newer version of docker. But the system time within the container is correct, so I assume there is a syncing problem within openHAB.
I found some old threads (like this) that speak of a syncing mechanism from the system clock to the clock used by OH. Is this true?