Phase out Boost Crawler submodule in favour of Recacher

I am the maintainer of module Recacher (https://www.drupal.org/project/recacher).

Prompted by issue #2694399: Difference compared to Boost Crawler I had a look at Boost's submodule Boost Crawler (http://cgit.drupalcode.org/boost/tree/boost_crawler) and indeed I found that they are similar in terms of approach (detection of expiration, recaching on cron).

The main advantage of Recacher over Boost Crawler is that Recacher is cache backend agnostic (works with everything that integrates with the Cache Expiration module).
Also, it a cut-off point for the recaching process -- not in terms of time, like Boost Crawler, but based on a max number of URLs to recache on a cron run.
It also has a bit more fine configuration and reporting.

So my question is whether there is energy for phasing out Boost Crawler and updating the relevant bits of Boost's documentation so that users know they can use Recacher instead.

I am willing to work on that myself, and of course I am happy to grant co-maintainership of Recacher to the maintainers of Boost.