OK - that is great theory, which I fully understand, but in practice this is what I have seen in recent testing.
The new HM6010 DC Point and Accessory Module (PAC) module is the R8247 Point and Accessory Decoder (PAD) of the DC world, except it has themsame number of capacitors but they are half the value of the DCC module and we know the R8247 is no muscle mechanic when it comes to throwing solenoids, especially in pairs.
The basic HM6010 module design is almost the same as the R8247 apart from the HM6010 having blue tooth connectivity to the operating app rather than being hard wired to a controller and it also has a high amp output on one port to be able to drive a turntable motor.
The PAC unusually has two alternative modes of power - 15vDC i.e the same as Select and Elite or eLink or direct DCC track voltage as output by any of those DCC controllers. One would think the internal circuitry of the PAC would produce the same potential at the port outputs, but ...
... throwing points - on straight DC voltage the HM6010 is not that reliable, especially throwing paired solenoids, but power it from a DCC track voltage and there is a noticeable increase in throw potential. You can actually hear the difference in click between the two powering arrangements on this module, which is factory set at the default 100mS pulse. Work goes on to try various pulse durations on the HM6010 as is currently possible to set on the R8247 via CVs.
Given that the CDU output of these modules is governed by the capacitor value and quantity then one would expect the R8247 PAD to out perform the HM6010 PAC by a wide margin.
Now if we look at the new basic DC controller R7227, which has the same value capacitors as the PAC but only two rather than four, yet it will reliably throw a pair of solenoids on a standard 15vDC power input.
Open to further discussion.