Until such time as InterSystems provides synchronization for security components across mirror members, you can save a bit of effort by exporting them on the primary and importing them on the alternate server via the ^SECURITY routine in the %SYS namespace. At least you won't need to create them manually.
You can do the same for users, roles, resources and a few other things as well. All of these have ObjectScript methods for accomplishing the same in the Security package.
There really is no list of "Standard" settings. You can use whatever section name you desire and it will appear in the list of settings for the business host in the production.
Most adapters provide the settings Basic, Connection, and Additional. However if the setting you're creating doesn't fit any of those categories, you can create your own with the "MySetting:MyCategory" format.
The documentation for creating business host settings can be found here.
EDIT: After reviewing the documentation, I discovered that there are a set of predefined categories and they're listed here.
I'm not crazy about the change from "Services" and "Operations" to "Inbound Hosts" and "Outbound Hosts" respectively. Considering that most of the protocols we use are bi-directional (some more than others), the new nomenclature seems less accurate.