My take on the AlfaOBD approach is that it modifies the body computer programming to the strategy compatible with LED DRLs, in which case the necessary power is delivered to the correct pins and the behaviour of the LED DRLs is consistent with Fiat's implementation (and legislation).
As I say, I haven't tested it and am making an assumption, but commonly various functions and programming strategies are built into the BCM, but only those enabled that are necessary for the factory built vehicle configuration, and often all that is required is the change of a single byte in the proxi configuration file to enable or disable a particular feature. Fiat dealers don't have the software to do this and the official Fiat approach is that a new body computer has to be ordered, correctly programmed for LED DRL headlamps.
But I have programmed a 2 hour off delay in my uConnect VP2 radio by this method, as well as reconfiguring the number of speakers and balance/fade control, using AlfaOBD. The software function rewrites the BCM configuration file and you then carry out a proxi alignment to distribute the new configuration to the relevant nodes on the vehicle.
Similarly on my Volvo, a cruise control switch costs £60 from a Volvo dealer, plus around £400 charge to install the software to enable it. But the routine is already present in the body computer (CEM) and the "software update" is just a change to a single byte in the configuration file that was easily done with some aftermarket diagnostic software.
Similarly I changed the stop/start system default strategy, which Volvo say cannot be done, and installed a TFT instrument cluster in place of the analogue version - cost me less than £200, Volvo want nearly £1000 for the cluster change