Use ctools crud, instead of accessing the database directly

profile2_regpath_get_profiles() and other loader functions get the items directly from the database, bypassing ctools.

If I understand correctly how ctools works, if you export to feature and then deploy this elsewhere, the objects might not even be in the database, but defined in a hook instead. So the module would then fail to load them.

One example to look at correct (I think) ctools integration is the field_group module.
It has dedicated "crud" functions to load and save field groups, which are based on ctools, e.g. ctools_export_load_object(), instead of calling the database directly.

See http://www.drupalcontrib.org/api/drupal/contributions%21ctools%21include...

I mark this as "Bug report" because it might already be a cause for misbehavior.
If this is not the case, it can be turned into a "Task".