Raster-based files of things like logos, when supplied by customers, often stink. A JPEG is fine if all you need to do is print an image of it at a modest size.
I'm not printing with them. I'm digitizing directly on top of them. Vector or raster files are just an intermediary step for me. Nothing more. Downside is if I'm even given a vector, it may not work for what I need, because it wasn't designed for physical production. So really, the only thing that I'm dependent on is good resolution that allows me to work 6:1. Other then that, it doesn't matter. Sometimes raster files work better as I don't have to deal with other issues at all, such as font substitution, gradients etc. In fact, gradients in vector form do not turn out right going through my program at all, it would have to be rasterized (which my program can do on the fly).
I'm not a fan at all of running emulation programs. Paying a lot of money extra to buy a Mac only to run emulated Windows programs on it seems like a whole lot of extra trouble and expense to go through to avoid running the same program natively on a Windows-based PC. Other people may look at the situation differently, but for my own case I'm sticking with the PC platform for desktop software purposes. If Corel goes out of business I'll even keep a museum piece computer running to keep the software alive. I have one old machine running CorelDRAW 9.0 that's good for opening really old CDR files the current versions no longer open.
WINE isn't an emulation program, it transfers Windows system calls to Unix (Linux and Mac) system calls. No emulation. Along the lines of what Windows is doing with the Linux Subsystems, but a little further along. Windows can only translate CLI programs (without doing workarounds that aren't supported), WINE handles GUI applications (since that's what Windows really is now since discontinuing 9x (at least the early yrs of 9x), is GUI).
Now as far virtualizing goes, pretty soon it's going to be hard and harder to source parts for that physical "museum" piece to the point that you are only going to be getting refurbished parts. May or may not last long. With virtualization, I don't have to worry about that. Plus, I've got a smaller footprint to deal with. On my main workstation, I can run 4 OSs at one time, on one computer. Linux host (no Mac cost there to worry about), Win 98, Vista, and Win 7 (sometimes this gets substituted for Win 8.1). All on a computer (at least this particular one) that's just 2 yrs old.
EDIT to ADD: Bare in mind, none of what I suggested is actually emulation in of itself. Most emulators will use software to handle hardware as well. VMs (which would be the closest thing to emulators) do not do this. They pass through the hardware to the VM itself. At least it's identifiers. This is why you can't run ARM OSs on x86 hardware. Or the reverse, run a hypervisor on ARM to emulate x86 hardware. True emulators will be able to do this.
Now, if we were talking about something like Bochs, then I would agree with you, but we are not. Emulators have a much harder performance hit compared to virtualizing the OS.