Explanation
Node taints cannot be used to schedule containers to meet the security policy requirements, because node taints are a Kubernetes concept and not a Swarm concept. According to the official documentation, node taints are used to mark nodes with certain attributes that prevent pods from being scheduled on them unless they have matching tolerations.
References: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

Explanation
Setting INSECURE_REGISTRY in the /etc/docker/default configuration file is a way to configure the Docker engine to use a registry without a trusted TLS certificate. The INSECURE_REGISTRY option allows you to specify one or more registries that do not have valid TLS certificates or use HTTP instead of HTTPS. This option bypasses the TLS verification for these registries and allows Docker to pull and push images from them without errors. However, this option is not recommended for production use as it exposes your registry communication to potential security risks. References: https://docs.docker.com/registry/insecure/,
https://docs.docker.com/engine/reference/commandline/dockerd/#insecure-registries