Well, if you'd done just a little bit of research you would've known that the CR was rewritten to allow both filesystem and db storage of content, so there's no need to propose a solution to this already-solved problem.
And you would've known that there's interest in supporting non-db indexers and that the decision to use OpenFTS wasn't meant to preempt the adding of other search technology in the future.
If you're interested in helping, you could, for instance, offer to help Neophytos and Dan implement a reasonable abstraction layer to tie together the site-wide search and content repository package. They might take you up on your offer, or they may not. They own these tasks and it is up to them. They may not be interested in addressing anything at the moment beyond making the handling of intermedia and OpenFTS transparent a the client level in our first release. If that's true, I'll support them, because we need to get this release rolled out in a matter of weeks, not months, if at all possible.
If you do want to help, you'd better hurry - Neophytos is planning to dig into the site-wide search package this weekend. He works fast.