The thing is that we are talking a bit different things. You seem to be in a case where you also need to cater for non-OCaml users on a dedicated website. odoc can certainly be twisted into that but that’s not odoc’s primary goal which is zero-effort doc generation and deployment for OCaml libraries and tooling (not only API docs, that includes tutorials, cookbooks, reference manuals, sample code etc.)
Interoperability or use of docusaurus will not enable better documentation user experience as far as OCaml programming is concerned. In fact if people start using it, it will make it worse (the reason why has already been mentioned but for a concrete example the day I want to use say @mbarbin’s CR I will hate the fact that I have to read a tutorial on that docusaurus website rather than an odig doc crs away, another one is the documentation of js_of_ocaml which I always have to consult on the ocsigen website).
So personally I think it’s a waste of time of odoc’s scarce ressources to multiply the half-baked backends and/or focus on this rather than having an excellent odoc system that provides an integrated and consistent documentation experience for programming in OCaml.