It might be worth considering whether a configuration change (or a delayed initialization) is affecting how audio/video devices behave.
I’ve seen a similar case here:
In that case, restarting the PipeWire-related services helped resolve the issue:
systemctl --user restart pipewire pipewire-pulse wireplumber
It’s not always a permanent fix, but it can help narrow down whether the problem is service-related.
Let us know if it makes any difference!