NodeClockContext was introduced in #34479 as a small RAII helper for tests and fuzz targets: it sets mock node time on construction and resets the global mock time on destruction. The motivation there was to make mock-time usage less error-prone and to avoid mock time leaking from one fuzz input to the next.
All current in-tree uses of NodeClockContext pass an explicit time, e.g.
0NodeClockContext clock_ctx{ConsumeTime(fuzzed_data_provider)};
The no-argument constructor is not used anywhere.