Yes, there are many ways doing it.
In high level, you have two options basically:
Implement a REST service in Hippo, which imports data from RSS feeds, periodically.
Or implement a Groovy Updater script, which imports data from RSS feeds, periodically.
For the option #1, you can choose either Repository JAX-RS Component solution [1] or HST Plain JAX-RS Service solution [2]. In both approaches, you have to configure a CRON job somewhere externally.
In implementation level, with Repository JAX-RS Component approach, you cannot use HST-2 APIs (e.g, HST-2’s WorkflowPersistenceManager [3]) unlike the HST Plain JAX-RS Service solution approach. You need to stick with either low-level JCR API or Repository Workflow API instead. In that case, Content-EXIM’s DocumentManager would help a lot as it provides a high level abstraction for you. [4]
For the option #2, take a look at [5]. You can schedule it with the forge module [6]. As the scheduler works in the repository itself, it’s more convenient and cluster-safe.
In this option, you can’t use HST-2 API either. You need to stick with either JCR or Repository Workflow API, possibly compensated by Content-EXIM core library (e.g, DocumentManager).