Questionable parameters in 'monitored_event' BCP messages

MPF version: 0.57.3 If a media controller previously asked to be notified about MPF events using the command monitor_start?category=events, MPF will send a message with the command monitored_event and a parameter event_name containing the name of the event each time an event is triggered is in MPF. So far so good. There are several other parameters passed in these messages though. Here's an example:

{
    "event_name": "modes_active_modes_changed",
    "event_type": null,
    "event_callback": null,
    "event_kwargs": {},
    "registered_handlers": [
        [
            "<bound method BcpInterface._send_mode_list of <BCP Interface>>",
            1,
            {},
            "0b19a5ba-2f73-4c47-b6a3-a8f8628eaeba",
            null,
            null
        ]
    ]
}

Is this intentional? I cannot imagine how these other parameters could possibly ever be useful in a media controller.

missionpinball / mpf

Questionable parameters in 'monitored_event' BCP messages #1849