Hiding NTFS Volume Names in the Finder

JUST to put some finality to my original question.. I was way overthinking things! I decided to repartition one of my drives into a NTFS volume (where I'll clone my win 10 derive) along with a bootable macOS so I had even MORE drives showing in the Finder. Slapped myself upside the head when I remembered there WAS a Finder option to hide everything except my boot drive... boom task accomplished. They are still hanging out in the sidebars to Finder windows, so I am not all that cut off from them.

Seems I can't edit my own post... figured out how to change the volume name in 10, so the only issue is hiding that one "System Reserved" volume from showing in the Mac Finder.

Found some advice about hiding or even preventing volumes from mounting in macSO... apparently it does with with NTFS volumes (using vifs to create a ftsf document... the implication is these volumes do not mount under macOS). Can't imagine WHY I would need to see these volumes mounted in the Finder anyway (yes I COULD buy some extra software that would allow me to write to NTFS volumes), BUT right now I can not see any of my Mac drives IN windows, so am pursuing that avenue before doing anything.

/dev/disk6 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

/dev/disk0s1 on /Volumes/System Reserved (ntfs, local, read-only, noowners)

/dev/disk1s2 on /Volumes/Clone (hfs, local, journaled)

/dev/disk2s2 on /Volumes/Spare (hfs, local, journaled)

/dev/disk0s2 on /Volumes/Windows10 (ntfs, local, read-only, noowners)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

/dev/disk3s2 on /Volumes/TimeMachine (hfs, local, journaled)

Obviously, it's disk0 I am interested in. Obviously, I CAN move files back and forth via a FAT32 stick... or do I want to write files from each to the other directly? MANY other options, I'm in fact finding mode now!

Gee, ya wanna know ALL my secrets,<lol>? Indeed I have 4 SATA drives (boot volume is an array on a pci card), yup, disk0 sure is my win10 drive; EFI, GPT, MBA all drove me nuts getting it installed... yes there are the 2 partitions, I am kinda thinking out loud about what I ultimately want to do, one option I am exploring here was to hide or prevent mounting in macOS. Yes, I THINK I know the implications (no Finder file copies to the main NTFS drive as that only come with software I have to buy):

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *500.1 GB   disk0
   1:               Windows_NTFS System Reserved         607.1 MB   disk0s1
   2:               Windows_NTFS Windows10               499.5 GB   disk0s2

Oh, nothing serious, I'd just rather not have to see it taking up spaces on my desktop, so convenience. I DO have this battle with keeping too much stuff always available on the desktop! Sense of elegance!

I try to not go into the long story, many get bored and ignore, but I think I got your interest! Machine is a 2010 true 5,1 vintage firmware (Boot ROM Version: MP51.007F.B03). It HAD been partitioned and bootcamped with win7, then literally half an hour before Redmond shut down the free win10 upgrade, I went for it. Yeah, the MSR never showed up in the Finder. Few years back, one fine day that install blew up, think I was installing the Logitech mouse drivers for my G700... and it would NOT repair itself no matter what. Recently wanted to get it rolling again. BUT my boot vol. was a PCI based array of SSDs. Got a 500G SATA SSD, stuck it in Bay 1, wanted that to be my win10 install. I tried SO many ways to make it happen, HUGE time investment as neither company makes it at all smooth or easy. PLUS I did NOT want to pull my boot out of the machine, it's in there and working great, and MOST likely nothing bad would happen, BUT... you get the picture!

Got the official iso from m$ (made the huge mistake of burning it in the Finder, that wasted 3-4 days of it not working at all). Reburned 1809 iso from the command line, THAT disc booted the machine. EVENTUALLY I dropped into the win command line to wipe my target drive clean (nothing I tried to do IN THEIR UI worked), then the install FINALLY ran. Nothing I tried in prepping that drive outside of their environment worked at all.

The GOOD NEWS is it seems their activation servers STILL after several YEARS later, have a record of my UUID and activated the puppy during the install! Ya got my diskutil list above, here come the 3 infos:

diskutil info /dev/disk0
   Device Identifier:        disk0
   Device Node:              /dev/disk0
   Whole:                    Yes
   Part of Whole:            disk0
   Device / Media Name:      Samsung SSD 860 EVO 500GB


   Volume Name:              Not applicable (no file system)
   Mounted:                  Not applicable (no file system)
   File System:              None


   Content (IOContent):      FDisk_partition_scheme
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified


   Disk Size:                500.1 GB (500107862016 Bytes) (exactly 976773168 512-Byte-Units)
   Device Block Size:        512 Bytes


   Read-Only Media:          No
   Read-Only Volume:         Not applicable (no file system)


   Device Location:          Internal
   Removable Media:          Fixed


   Solid State:              Yes
   Virtual:                  No
   OS 9 Drivers:             No
   Low Level Format:         Not supported
   Device Location:          "Bay 1"

diskutil info /dev/disk0s1
   Device Identifier:        disk0s1
   Device Node:              /dev/disk0s1
   Whole:                    No
   Part of Whole:            disk0


   Volume Name:              System Reserved
   Mounted:                  Yes
   Mount Point:              /Volumes/System Reserved


   Partition Type:           Windows_NTFS
   File System Personality:  NTFS
   Type (Bundle):            ntfs
   Name (User Visible):      Windows NT File System (NTFS)


   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified


   Disk Size:                607.1 MB (607125504 Bytes) (exactly 1185792 512-Byte-Units)
   Device Block Size:        512 Bytes


   Volume Total Space:       607.1 MB (607121408 Bytes) (exactly 1185784 512-Byte-Units)
   Volume Used Space:        416.0 MB (416026624 Bytes) (exactly 812552 512-Byte-Units) (68.5%)
   Volume Available Space:   191.1 MB (191094784 Bytes) (exactly 373232 512-Byte-Units) (31.5%)
   Allocation Block Size:    4096 Bytes


   Read-Only Media:          No
   Read-Only Volume:         Yes


   Device Location:          Internal
   Removable Media:          Fixed


   Solid State:              Yes
   Device Location:          "Bay 1"