Allow RedHen Data Synchronization Functionality to Be Used Without Making the User Manage the RedHen Contact

There are a number of functions in RedHen CRM that allow for synchronization of data between a Drupal User and their associated Redhen Contact. These are useful functions and contribute greatly to the ease of use of RedHen; however, in some cases the functionality that is built assumes that the User will manage their own RedHen Contact and when that is not the case somewhat restrict's their ability to manage their account as a result. In some CRM use cases the CRM is used to manage information that is exclusively for the Site/CRM Administrators and should not be shown to the User.

The assumption that the User will manage their own contact exists in (at least) two function sets as exposed by RedHen settings:
a) Email Settings -> 'Mirror RedHen Contact email to Drupal user'
b) User Registraiton -> 'Create a contact during user registration'

I propose that these function sets be both retained and refined further to support the use case above.

For a)
It may be enough to continue allowing the user to edit their e-mail address in their User Account page and copying the edited e-mail over to their RedHen Contact once the change is saved. If we want to create a record of past User E-mails then we could create a new row in the RedHen Contact E-mail list with a label of 'Past Address #' and update their Primary Contact E-mail. (There are a number of options for naming and saving an old e-mail address in addition to this one.)

For b)
A RedHen Contact requires a First and Last Name. Perhaps making an option to allow showing only those fields would work? A basic 'ACL' for each RedHen Contact Fields choosing which to expose on the /user/register form would also be an option.

Thoughts?

Best,
Raxx