Cloudera Manager Agent Instance of Supervisor conflicts with System Supervisor

Cloudera Manager Agent spins up its own custom configured copy of supervisord which uses the default application port but different configuration directories and is managed by Cloudera Manager. This causes the system instance of supervisord to break depending on which copy is loaded first. Can this special instance of supervisor be set to a different default port in the next release?