How so, given that we immediately re-enable the same swap device right after so that it’s only off for a very brief moment? Let go :)

$ free -m
              total        used        free      shared  buff/cache   available
Mem:           64141       17213       24010        1984       30297       46927
Swap:          20479           0       20479

See that buff/cache column? That's memory being used by the system for caching. Files you you open and access get cached into memory as do inodes, filesystem objects, etc. If you run a "find / -type f" twice in a row the second one will be significantly faster because the first run cached a lot of objects into memory.

By starving the system of memory all that will be flushed and you get more disk access doing things you're actually trying to do. Whereas things sitting in swap are there because they aren't currently needed.

By turning off swap and then back on again you're just forcing the system to drop all that cache which it will then attempt to reclaim space for and push things back out to swap.

I don't know what benefit you think you'll gain in the process.