ConfigMap always interprets file

Cluster information:

Kubernetes version: newest supported by Rancher
Cloud being used: variable
Installation method: Rancher
Host OS: variable
CNI and version: variable
CRI and version: variable

I’m sitting for hours on this issue and can’t seem to find a suitable fix.

I am trying to mount a file through a ConfigMap as is, without interpretation of the mounted files’ contents.

I managed to exclude all other possbilities by writing the file literally, calling it literally, encoding it as binaryData, etc. The only step that I could not force to be literal, is the mounting of the ConfigMap’s content.
During the mount process, all backslashes are removed, except when they are escaped with an additional backslash. I want to have the data in a ConfigMap mounted as is, without any alteration.

How can I achieve that?