1. The Mach-O executable format was not changed between all those OS versions (likely).
2. It is possible to gather sub-binaries for one CPU type but different OS types (less likely).
And SDK's and compillers (in emulator or on hardware) are required to try.
http://tenfourfox.blogspot.com/2020/06/the-super-duper-unive...
Previous Hacker News discussion
But enough about my private life. You're making us blush
It seems that this early version is significantly different from later NeXTstep (3.3) and OpenStep versions. For example, it does not use app bundles. System apps installed in the /Apps folder, such as Terminal, are simple Mach-O executable m68k binaries.
If we wanted to target such an early NeXTstep, in addition, the source code of TinyClock would have to be changed significantly. One problem is that early versions of AppKit used "NX" instead of "NS" prefixes. More difficult is that a number of classes used by TinyClock seem to be unimplemented - not even NSString (resp. NXString) seems to be available. More complex classes such as NSCalendarDate or NSBezierPath also seem to be a later addition (unless the 0.8 install image is missing some header files, the earliest documentation I could find was on 1.0).
So it seems that a completely universal binary is out of the question, unfortunately.