So I was reading about installing content types as features and saw the
following:



msdn2.microsoft.com/en-us/library/aa543504.aspx

Do not, under any circumstances, update the content type definition file
for a content type after you have installed and activated that content
type. Windows SharePoint Services does not track all the changes made to
the content type definition file. Therefore, you have no reliable method
for pushing down all the changes made to site content types to the child
content types.

So, what kind of change management is available for these custom content
types? If best practice is not to update the definition file and
redeploy the feature, what is the benefit of rolling content types into
a feature rather than just adding them from the interface to begin with?

There is no better means of promoting another person's change of heart

than allowing our own heart to be changed.