1) the ID is absolutely part of the ecosystem, and one of the uses would
be that "gateway" or local processing FPGA bitstreams are either
selected from pre-compiled pool, or generated on the fly either locally
or in the cloud

the ID system may have to be hierarchical -
BOARD ID
FPGA ID for the primary boot partition if multiboot capable FPGA
ID for the FPGA application image that is currently loaded

lots of work, for later, but initially only some board-id part is
relevant as it "hardened" while the rest is kinda soft..