[Questions] Usability of Diskeeper\'s "IntelliWrite" Filter Driver

Diskeeper’s Intelliwrite seems to be nothing more than a filter driver?
A .sys file that can be added to Device Manager using the ‘Have Disk’ method.

Question is:
Do filter drivers rely on other files to work correctly?
Or can one simply experiment with the .sys file, DKRtWrt.sys downloadable from here:

Or are other supporting drivers and files required??

Diskeeper is who Microsoft turns to for disk maintenance software:
The Windows Defrag app is from them.
The full version does a lot of stuff to 1st avoid drive fragmentation and also defragment them.

One of the most interesting to me is the intelliwrite function that avoids file fragmentation on initial write and (read/write caching, defrag, etc is available elsewhere) reads:

Picture the disk map, in your fave defrag app, of a fragmented drive.
Remember al those little free space gaps…
When windows writes a file to file to the drive it tends to split the file of into small pieces to fill those gaps.
That’s not good!:

For SSD and HDD it means that the initial write and all subsequent reads, that could have been large large sequential I/O is turned into small random (4K) I/O
We all know how much worse random I/O performance is on both SSD and HDD.

On SSDs it also means that a more than necessary number of Erase Blocks have to be read, modified, written. A process that wears out Flash memory.

Info on Intelliwrite:


EDIT by Fernando: Thread title shortened

I still use Diskeeper’s feature until now on Windows 10 and still doing wonders for me for over 3 years it is a must for any storage devices no matter what to be honest.