Hi,
This sounds just perfect to me. Because the content to be indexed is placed to the actual post_content field, then any search plugin (or any plugin for that matter) can utilize it – it is not limited to ajax search pro only.
If you prefer to leave the post_content as it is, you could use a custom field as in the original code, I think both solutions are perfectly fine, I don’t think this causes any issues.
I will look into this, it seems very interesting. Maybe we can figure out a way to one-click download and execution for it via the plugin back-end.