Proposal: Custom CSS class for honeypot fields

I notice from time to time that honeypot fields are shown to the user in the frontend. I can see that

style="display: none;"

is written as an inline css command in the divs that form protection produces. So I really don't have a good explanation as to why some fields are shown in the frontend nonetheless.

Anyway - a possible workaround might be to let users choose a custom css class that is added to the divs of the honeypot fields. This way users might get a better handle on supressing the fields in the frontend.