A generalization might be a good idea. I’m not quite sure how useful it would be because the different clocks generally serve very different purposes.
Time::Instant should work as a name for that.
I don’t think it’s a good idea to integrate wall clock into scheduling primitives.
The wall clock is volatile and might show erratic behaviour sometimes.
Also the behaviour of such a method would not be entirely obvious: Does it convert the wall clock into a monotonic clock right away or does it somehow monitor the wall cloc to trigger when it reached the given instant? The former would probably be better to explicitly convert to monotonic time at the call site. The latter seems way to complicated for a scheduler function.