I’m experimenting with putting the call to include user.functions.php in a function hooked to prodigy_init at a priority of 11, so that it gets called after the entire Prodigy framework is loaded.
This would eliminate the need to remove_actions in a function attached to prodigy_init in the user.functions.php file, as well as allow the user.functions.php file to take advantage of functions created in prodigy.
Bottom line, I’m trying to help you avoid the unnecessary nesting of functions just to get simple things to work.
I’m hoping there won’t be any serious repercussions to doing it this way. So far, I can’t think of any.