Not meant as an answer to the problem. Only explaining why "You just cannot!" is the only possible answer to the question as worded in the title :

It is indeed possible to pass boot parameters of the kind :

module_name.parameter_name=parameter_value

Which will be honored by some in-kernel built module_name driver at the condition the driver accepts the parameter_name and parameter_value is within the ranges of accepted values.

The usb-storage driver would for example be able to ignore one particular usb storage device using a boot command line parameter of the kind :

usb-storage.quirks=03f0:b002:iu

Because the usb-storage is programmed in order to honor the quirks parameter and decode its value as representing Vendor-Id:Product-Id and i meaning IGNORE_DEVICE.

If the uvcvideo driver does honor a quirks parameter, it unfortunately, offers no particular value forc that parameter aimed at disabling the device.

Not meant as an answer to the problem. Only explaining why "You just cannot!" is the only possible answer to the question as worded in the title :

It is indeed possible to pass boot parameters of the kind :

module_name.parameter_name=parameter_value

Which will be honored by some in-kernel built module_name driver at the condition the driver accepts the parameter_name and parameter_value is within the range of accepted values.

The usb-storage driver would for example be able to ignore one particular usb storage device using a boot command line parameter of the kind :

usb-storage.quirks=03f0:b002:iu

Because the usb-storage is programmed in order to honor the quirks parameter and decode its value as representing Vendor-Id:Product-Id and i meaning IGNORE_DEVICE.

If the uvcvideo driver does honor a quirks parameter, it unfortunately, offers no particular value for that parameter aiming at ignoring any device.