If I specify hibernate.id.new_generator_mappings=true then the behaviour would be the same in all three, but I have to fix my application so that third party lib for db migrations will use the new naming strategy.

What does hibernate.id.new_generator_mappings have to do with naming strategies?

But there is another issue here. I want my application to be deployable to Wildfly 8, 9, and 10. I need a configuration setting that will work the same on all versions.

The problem is the split in the contract, not the setting name. WildFly 8 and 9 used Hibernate 4.x that had a contract (interface) that is no longer part of Hibernate 5. This is part of the reason for short-name settings, but bottom line is that we are not time travelers and cannot go back in time and "fix" 4.x.

So what exactly are you asking for here?