How to overcome Docker Hub download rate limit with Apicurio registry installed via OperatorHub?

[mzaikin]

Disclaimer: this is not a duplicate of the question I asked in the Issues section (#2009).

Current setup: Apicurio Registry Operator 0.0.4-v1.3.2.final installed in OpenShift cluster, use JPA as persistence.

I wonder if OpenShift is starting experiencing download rate limitation of Apicurio Registry image by Docker Hub, and pulls fail, and lots of pods in the crashed state, and editing of ApicurioRegistry's spec.image.name not switching to new [locally pulled] apicurio-registry-jpa image, even while operator's description says different:

 description: >-
              Override the image name according to selected Persistence Type for
              example,
              MEM="docker.io/apicurio/apicurio-registry-mem:1.3.2.Final"
              KAFKA="docker.io/apicurio/apicurio-registry-kafka:1.3.2.Final"
              STREAMS="docker.io/apicurio/apicurio-registry-streams:1.3.2.Final"
              JPA="docker.io/apicurio/apicurio-registry-jpa:1.3.2.Final"
              INFINISPAN="docker.io/apicurio/apicurio-registry-infinispan:1.3.2.Final"

I wonder how to overcome it?

Delete Apicurio Registry Operator and recreate ApicurioRegistry, providing from the beginning new local Docker image?

If yes, how fully clean up all objects related to the existing Apicurio Registry from OpenShift?

Is there any chance to keep old schemas we populated, i.e. keep Postgre, and when recreating registry, provide currently existing DB?

Appreciate any help or hint.