Because ntfs has been a proprietary filesystem, only rudimentary tools were ever created for Linux.
Some of those tools may handle superficial corrections such as cross-linked files, for example, but none afford the advanced functionality that only chkdsk can.
It’s unfortunate, as the advantage would otherwise be obvious – perhaps this will change if chkdsk is reverse-engineered by someone with the talent and time – but, for now, the recommendation stands to use chkdsk as described.
Note that a “Windows environment” doesn’t necessarily infer a fully installed Windows system:
In this case, the OP has a specific need for ntfs (or fat32), as they have described previously: