Handle edge cases in encryption

**Feature request**
It would be great to have caching for parsers.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_caching` with default `false`.

The issue names no files or tests. Start by locating parser entry points and configuration handling, then determine how parser results are produced and reused. Done means a new `enable_caching` option defaults to `false` and caching behavior is covered by appropriate tests, but the required cache scope and invalidation behavior still need clarification.

Written by the indexing model from the issue text.