Refine fluent API for boolean configuration properties

The following configuration properties lack an API mechanism for disabling their functionality once enabled:

invocationBatching
jmxStatistics

Some configuration properties cannot be re-enabled once disabled.
e.g. for indexing, calling config.fluent().indexing().disable().indexing() will disable then re-enable indexing. However, this does not work for the following properties:

l1Caching

While I'm at it, there seem to be 2 mechanisms for dealing with boolean properties.
Either the property is auto-enabled with an option to disable:
e.g.
config.fluent().indexing().disable()

or, the property is enabled/disabled explicitly:
e.g.
config.fluent().hashing().groups().enabled(Boolean)
config.fluent().hashing().rehashEnabled(Boolean)

Is there any reason why one approach is preferred over the other?