No. Camino was not a good alternative browser.
Camino was (is?) a Cocoa wrapper around Gecko, an engine for which OSX was a second class target, that steadfastly refused to use native components for basic UI (to this day there are basic OSX behaviors that gecko seems to struggle with), and was certainly not generically embeddable in other applications - Safari came with the WebKit system framework remember.
OmniWeb was similarly nowhere near the level of compatibility with real web content, and while obviously made by a Mac centric company, couldn't be used as a system component.
KHTML then has additional advantages - lower memory footprint, better responsiveness, designed specifically to be a component that could be embedded in arbitrary apps and used for non browser purposes.