v4l2 Virtual camera - Loopback device conflicts (Including droidcam)

Platform

Operating system and version: Arch Linux - Rolling
OBS Studio version: 26.1.0.r9

Expected Behavior

Clicking on "Start Virtual Camera" button should start the virtual cam flawlessly

Current Behavior

Pressing the button does not create any effect.

Steps to Reproduce

1. Install droidcam from @dev47apps**
2. Install obs-studio-git from AUR
3. Remove the old CatxFish/obs-v4l2sink plugin
4. Install v4l2loopback-dkms
5. Start OBS and click "Start Virtual Camera" button.

Additional information

The log says "warning: Failed to start virtual camera" when clicking on the button.
I've installed droidcam alongside OBS, and it currently uses the /dev/video0 device. I thought maybe obs is trying to use that device and it conflicts with droidcam, but disabling (not removing) droidcam doesn't solve the issue.

Edit:
I've tried removing droidcam, it turns out that they were indeed in conflict. Removing droidcam solves the issue, reinstalling it works fine, but as long as I reboot droidcam takes over /dev/video0 and I could not find any other ways than removin and reinstalling droidcam... every reboot.
It's solved in a way but that's not very practical.

Start by reproducing the failure with droidcam and v4l2loopback-dkms installed, checking the OBS log warning and which device is assigned at /dev/video0. Trace the Start Virtual Camera path and determine whether OBS can select or coexist with the device after reboot; done means virtual camera startup works without removing or reinstalling droidcam.