No.
In my day job, I'm a Unix file system developer. What you want to do is not possible.
From the perspective of the file system on the RAID, the disk image is a single file, and the external file system does not know anything about the structure of the file system inside the disk image. And there is "NO" API for removing storage from a disk image, along with all the metadata, and giving that to the enclosing file system as a new file.
What you want to do is like taking an upstairs ensuite bathtoom and moving it to the downstairs living room AND expecting the water to run, the toilet to flush without the plumbing and electrical hooked up. And the bedroom to automatic reconfigure itself as if the bathroom never existing in the bedroom. And the living room will dynamically expand to accommodate the bathroom without getting smaller.
A file consists of a file name stored in a directory. The directory basically has the file name and a pointer to the file metadata stored elsewhere in the file system (metadata keeps track of file storage, ownership, permissions, file attributes, etc....).
Moving a file without copying basically involves deleting the current directory entry, and creating an entry with the same name in a new directory. The new directory still points to the same metadata that is keeping track of your file.
The primary restriction for moving a file without copying is that both directories must exist in the same file system.
What you want to do is move a file between 2 file systems, and that involves copying the data and creating new metadata in the destination file system.
If you can keep the disk image mounted, or at least mounted when you want to access this file, you could create a macOS Alias in the RAID based file system that points to the file in the disk image. A macOS Alias should work for any GUI based app. One advantage of an Alias is that it should automatically mount the disk image. The disadvantage is that an Alias will only work with GUI based apps.
If you want non-GUI base apps to access the file, then you could create a symbolic link via either a 3rd party GUI based utility that will create symbolic links, or you could create it from an Applications -> Utilities -> Terminal session:
ln -s /Volumes/name-of-disk-image-when-mounted/path/to/file /RAID-file-system/path/to/where/you/want/to/use/the/file
Google can help you with examples on creating symbolic links.
The advantage of a symbolic link is it will work with any application. The disadvantage is the disk image must already be mounts, as the symbolic link will not trigger a mount.
