It's possible and quite simple to do just that. NHibernate allows us to specify access strategy for individual property. I'm frequently use something like this:
protected District _district;
public virtual District District
{
get { return _district ?? this.Zone; }
set { _district = value; }
}
And mapping for the property:
<property name="District" access="field.camelcase-underscore" />
In this mapping scheme, your code will use the property to get/set data, while NHibernate uses the field to do the same. If you leave out the access setting, in case the property District is really NULL, NHibernate will think that you have changed the property District to the new value and it will try to update the corresponding database record. This might result in bugs.
I've never used Fluent NHibernate, so I don't know how to do that with Fluent.