I kind of get what you’re saying…I think. I also think that Wyze primarily sees this as a camera product and so treats it that way, because it doesn’t behave like (or have the same controls as) their lighting products. In fact, the Accessory Bulb—without a bound Bulb Cam—behaves just like a “dumb” LED. The FAQ section of Accessory Bulb’s product page even says this:
Without the Bulb Cam, your Accessory Bulbs will only function like normal (not-smart) light bulbs.
To my thinking, that indicates that Wyze sees even Bulb Cam as a camera product first and as a lighting product second.
Having said that, because of the way you’re trying to trigger your lights and because you’re using two separate Bulb Cams instead of a Bulb Cam plus a linked Accessory Bulb (which is what I have outside my garage), I think you could probably accomplish what I believe you’re trying to do if you used a secondary product that actually does support a “Has been on for” Trigger and/or “Turn on for” Action. Something like a spare Wyze Plug (or an outlet on a Plug Outdoor) or one of the regular Bulb products (I haven’t tried Bulb White but know that Bulb Color supports those) could be triggered on by motion and then used to turn off (also via Device & Service Trigger) the Bulb Cams’ lights after a user-determined time. You’d just need for this secondary device to be connected to power and Wi-Fi so that you could incorporate it into the relevant Automations that you’d create for the task.
Something else you could do is visit the following Wishlist topics:
In each of those, you could hit the Vote button above the initial post and then add your ideas and use cases in the comments to show your support for what you’d like to see (expanded Actions for Bulb Cam, for instance). If you want a more immediate solution, however, your best bet—again, if I understand your goal—is probably going to be using a secondary product as an intermediary for an Automations work-around.