Not to minimize your efforts on enabling swap, but the long boot time happens not because there's no swap, but because there's a swap entry in /etc/fstab that points to an invalid (non-existent) partition. Therefore, some init scripts invoked by systemd at boot time enter a wait loop, just in case this partition becomes available after some time. This invalid entry in /etc/fstab has been identified by another user here in the forum some posts ago, and just commenting it out solves the long boot time.

Now, if someone actually needs a swap partition, that's a different story... From my experience (and some other users as well), with 4 GB+ of RAM, there's no need of swap. I kept monitoring my RAM usage, even with Claymore's dual-mining, and it never came close to requiring swap. Now, going a bit more technical, if you were using your operating system in a different scenario (heavy multitasking, VM host, database server, desktop system where you need suspend-to-RAM etc.), you *may* benefit of a swap space even with enough RAM (and in case of suspend-to-RAM, you do need it, and at least the same size of your installed RAM), because the operating system may decide that it would be best to swap old memory pages to disk instead of purging them from RAM (and this "swappiness", in Linux, can actually be defined at runtime, i.e. you can instruct the kernel how agressively it should swap memory pages to disk). I don't think mining fits in these scenarios, and a swap space in a very slow medium like USB stick doesn't make much sense (I know in your case you used a SSD, but that's an exception). In Windows, Claymore requires a huge swap space because of different reasons (and Windows virtual memory management is different than in Linux).