Well, it's a pretty moot point regardless of whether or not I have the CPU horsepower to calculate a MD5/SHA-1 hash with the MCU in a reasonable amount of time. I just grabbed a
public domain MD5 implementation and compiled it in, and it's ballooned my firmware size way over the amount of flash space available. So constructing a Version 3 name-based UUID on-device is out.

I was really hoping to have a common firmware image that can be just programmed as-is onto every device, hence why I was hoping to take advantage of the MCU's unique hardware ID.
If I wanted to generate the UUID at programming time based on the chip's hardware ID, I would have to re-compile the firmware for each and every device, because I don't have any NVRAM (e.g. EEPROM) to store it separately. I would really rather avoid a distinct firmware image per-device.
I wonder if perhaps I could do the following:
- Generate a single 'master' Version 1 time-based UUID.
- Include that in my firmware.
- On-demand, substitute the most-significant 48 bits (the 'node' field) with part of the MCU's hardware ID.
I mean, the MCU's hardware ID isn't too different from a MAC address (what conventionally goes in the 'node' field), is it? I would just need to determine what part of the chip's 64-bit (or 96-bit? - TBD) hardware is suitable for truncation to 48 bits. If the manufacturer bases the hardware ID on a serial number, then I suppose there may be certain bits of the ID that are more likely not to change from chip to chip.