If a custom field matches the name of a join, it could mistakenly register that join as used. This is because custom fields are expressed without a view scoping (viewname.fieldname) and are simply listed as their field name (fieldname). So if that fieldname matches a real join in the explore, it will interfere with Henry.
In the fetcher.py module