Why are command probes patched 1 by 1?

[madman2003]

I just had to add this to make two probes from near future work:

// N-Series Guidance Computer Unit
@PART[drone-core-5-1]:AFTER[NearFutureLaunchVehicles]:NEEDS[RemoteTech]
{
        %MODULE[ModuleSPU] {
        }

        %MODULE[ModuleRTAntennaPassive] {
                %TechRequired = unmannedTech
                %OmniRange    = 3000

                %TRANSMITTER {
                        %PacketInterval     = 0.3
                        %PacketSize         = 2
                        %PacketResourceCost = 15.0
                }
        }
}

// E-Series Guidance Computer Unit
@PART[drone-core-75-1]:AFTER[NearFutureLaunchVehicles]:NEEDS[RemoteTech]
{
        %MODULE[ModuleSPU] {
        }

        %MODULE[ModuleRTAntennaPassive] {
                %TechRequired = unmannedTech
                %OmniRange    = 3000

                %TRANSMITTER {
                        %PacketInterval     = 0.3
                        %PacketSize         = 2
                        %PacketResourceCost = 15.0
                }
        }
}

But why aren't these patched like mechjeb4all using a generic statement?:

@PART[*]:HAS[@MODULE[ModuleCommand]]:NEEDS[kOS]:Final
{
    MODULE
    {
        name = kOSProcessor
        diskSpace = 10000000
    }
}

[KSP-TaxiService]

Hi, it is for backward compatibility on older KSP versions. For example, your new MM patches to KSP 1.5 probe cores _v2 will be safely ignored on older versions.

Hope this clarifies your question