Sorry, basically, I have my MacOS on my 256gb ssd and my Windows 10 install on my 1tb platter, so separate drives. They were both booting perfectly, both just single partitions on separate disks obviously other than the EFI and whatnot. I didn't have any usb's spare so I ended up wiping the Sierra usb to use for the windows side. What's this whole flag thing? and I edited the plist in clover yeah. Sorry if my method sounds sloppy, but I'm fairly new to Hackintoshing. Shoot me.
Since you don't have the Sierra USB installer you may not be able to boot through Clover to reach your desktop. If you can create one the way you made it before or get even an el capitan USB installer, you can get to the boot menu and then boot your Sierra and re-edit Config plist to get back to previous state.
If you cannot get any USB OS X installer, you may try to boot to your Windows HDD by going to BIOS and making it first boot device and pressing F12 selecting that and boot through Windows Boot Manager. Some times you may even have to Reset CMOS jumper on your MoBO , Load Optimized Default BIOS before you can boot from Windows HDD as first Boot device.
Later you can borrow a USB installer from your friend to troubleshoot and revive your Sierra System.
Since you did not answer the question about the Windows installation mode (legacy or UEFI) , I assume you used the Windows 10 DVD to install it. In that case you might have made a Legacy Windows installation. If your MacOS Sierra was in a UEFI Clover Mode , Windows would not be accessible through Clover Boot Manager.
For a Dual Boot Windows and Mac or triple boot with Linux included to boot using CLOVER EFI Boot-loader, ALL Systems must be the same Boot Mode either ALL l Legacy or All UEFI; otherwise those not sharing Mac's Boot mode will not be seen in the Clover boot menu.
PS. I should stand corrected. You mentioned you used the FD to create the Windows System . If you have used RUFUS and made GPT /NTFS , you might have had Windows in UEFI and both systems might have been UEFI boot mode.
In that case you might have inadvertently selected to "Scan Legacy" in your original CLOVER>config.plist which would have created a lot of Bogus entries in your Clover Boot screen that must have been an eyesore and you might have done something to get rid of them by re-editing your config.plist and caused the problem.
In any case they are all fixable if only you have a OS X or macOS Sierra USB Installer.