I don't like the idea of a sparce file system on principle, too much experiance with fragmentation, I suppose. However, this utility is an interesting option because when using the /EXE option it doesn't compress files added to the directory after the utility is run, eliminating fragmentation but increasing the total writes because compressed files are entirely rewritten in uncompressed form when they are edited. The compression process also increases total drive writes because it has to rewrite the entire file in compressed form.
Theoretically access times for very small files would increase but the load times for large files with large blocks of 0s would be much faster, loading an extra table of 0 blocks takes more time for small files but much less time for large ones.
However, large video files or other already compressed files do not have large blocks of 0s in them because they already use effectively similar compression methods that are actually more efficient but take much longer to encode (along with much more complex methods that are very different and take a relatively unbelievable amount of computation).
I think this is doing more compression than simply enabling a sparse file system, EXPRESS4K probably does extra, very fast, compression optimized for executables and libraries.
I would simply use the command line utility directly:
Microsoft Windows [Version 10.0.16299.19]
(c) 2017 Microsoft Corporation. All rights reserved.
Displays or alters the compression of files on NTFS partitions.
COMPACT [/C | /U] [/S[:dir]] [/A] [/I] [/F] [/Q] [/EXE[:algorithm]]
COMPACT [/CompactOs[:option] [/WinDir:dir]] [filename [...]]