So long as the identifier is
constant over time that does not matter.
From your reference:
UAS ID Type 1. Serial Number, 2. Registration ID, or 3. UTM U
(page 10)
That is: there is a single identifier, constant over time, that is assigned to each drone aircraft.
The UUID standard appears to be RFC 4122:
https://www.rfc-editor.org/rfc/rfc4122
And again: so long as that's transmitted in the clear, ANY party may accumulate a database of UUIDs and locations over time, which would tend to identify the party(ies) associated with a specific drone. That might not be precisely the operator, but if drone ID "8daf5e654951a033175fb71e0a2ecc03"[1] keeps showing up at Your Fine City's Police Department ... or sewage department, or electric utility ... you might begin to draw some inferences regarding its likely owner/operator.
It might be easier to do so if the identifier had, say, a specific entity element to it (say, as with LDAP or X.500 entity attributes), but the lack of such an element to the identifier itself is at best a small hinderance to owner/operator identification.
________________________________
Notes:
1. md5sum of the randomly-selected string "random drone id"