How to defragment by the contents of folders and does it make sense?

Question

NTFS

Hello colleagues. I have a few questions about defragmentation.
New files fill the free space from the beginning of the disk, and if the free space between other files is small, then the new file is split into parts (fragments), which affects the speed of reading these files. Defragmenter programs eliminate this by collecting fragments in one place in the order in which they appear. I also heard that the defragmenters that use WinAPI for this divide the disk into pieces of 64 kbytes (or bytes, I don’t remember exactly) and as a result there is some free space at the end of the file, where new files are then written and a lot of fragments are obtained more than in a short period of time. That is, the computer at the same time sits down on defragmentation, like a drug. But there are defragmenters that don't use WinAPI and fill in all (almost) gaps. I am using Vopt.
Why combine file fragments into a single block is understandable, but why don't defragmenters write the contents of folders together? After all, one program does not consist of one file, but can use several thousand files. Although they are solid, they can be located in different parts of the disk. That is, as if one file is divided into many files, and when the application is launched, the same fragmentation is obtained, but not at the level of file parts, but at the level of many files.
Are there any defragmenters that arrange the contents of a disk in their path? Thank you.

Answer 1

defragment by frequently run files