The best answer I have so far comes from:
https://www.rabbitmq.com/resources/specs/amqp0-9-1.extended.xml
Where it says:
<!-- For application use, no formal behaviour -->
<field name="app-id" domain="shortstr" label="creating application id"/>
<!-- Deprecated, was old cluster-id property -->
<field name="reserved" domain="shortstr" label="reserved, must be empty"/>
Whatever the cluster_id was for originally (identifying a cluster perhaps?) it is no longer used.
The comment notes "no formal behaviour" which I interpret as meaning that the header is permitted but it is entirely implementation defined and can be used for anything.
Given that you can also have custom headers (see this question for example) it seems odd (bad protocol design?) to bother having any headers that do not have well defined semantics of their own.