In order to stay in compliance with bluetooth specifications, the bluetooth stack is controlled to minimize incompatibilities.
But, you might be able to change the value in software rather than in the component configuration/settings.
Try setting the characteristic for CYBLE_UUDI_CHAR_APPEARANCE (0x2A01) to your custom value with code and see if the advertisement comes up with positive results for that.
Thanks for the quick response., I will try that. I understand the desire to enforce standard compliance but this is for a custom prototype application with only limited and specialized use. It would not be in mass production.
The compliance is more of simplifying the design-time for users from what I've seen, it might not necessarily be intended for forcing compliance. But that is a reason for not being able to change settings easily in the component configuration
If you manually change the flag data/bits in code, you might be able to get around the forced compliance, but I haven't tested/played with it so I don't know what you can do for that.