Not as standard. The unit of measure field you are looking at is the attribute unit of measure so wouldn’t be an ideal field to do this with.
Reason? The attribute table allows you to have a many to one relationship to the item table so which attribute uom would you use?
Attributes don’t need UOMs but a use case is where you record multiple attributes for a single item such as length, widths, weight, volume etc. each of these may have a different uom and none of them are necessarily the correct default uom for the item.
In most cases, a better way to achieve what you need is with templates. Assign a default category and uom in the template. Although I have found using power automate and forms allows structured item creation with more flexibility and less maintenance than templates.