Trivial to roll your own. Just create your own configuration variables in a properties files (or context.xml, etc) and build JmxReporter yourself from them. Look at the class com.codahale.metrics.JmxReporter.Builder.
I have a production app with configuration files for csv, jmx, graphite and cloudwatch targets, with different filters and groupings of jvm, servlet, ehcache, and the hikari connection pool. The production app checks for updates to these properties and reconfigures itself if they change. When you change properties, you'll need to close the existing jmxReporter instance then create and start a new instance.