You might have better luck with a negative custom field, i.e. 'Disable Feature X'. And then in the template check that field. I had the same issue and that is how i overcame this. Custom Fields to my knowledge cannot be setup with a default value for all members, unless done via something like an SQL query, but then you would have issues with new registrations after that query is run who would not have that value preset.