Why does the Device Update Agent not support client certificates?

[D-r-P-3-p-p-3-r]

The docs state

Accepted values are string or AIS. Use string when connecting the device to IoT Hub manually
for testing purposes. For production scenarios, use AIS when using the IoT Identity Service to
connect the device to IoT Hub.

Is there a reason authentication with client certificates is not supported by the Device Update Agent? The Azure IoT C SDK supports it and we're using it to connect our devices to the IoT Hub. It's very inconvenient that it's not possible to use the same mechanism for the Device Update Agent. To run the whole Azure IoT Identity Service stuff only to allow the Device Update Agent to connect to the IoT Hub (differently than the main app does) seems like overkill and a waste of system resources (RAM, Flash, CPU, integration, and update effort, ...).

I had a quick look at the code. Would it be possible to get the feature into the project if we develop it?

[D-r-P-3-p-p-3-r]

I implemented the feature in my fork of the repo. If there's any interest to get this mainline, please let me know.