@meeffe
I haven't had any issues like that and I have used the trick since the Sierra beta versions of macOS. I would still recommend making a Time Machine backup, just in case something goes wrong. This is sort of a drastic last-ditch hack, but in my case I have no other alternatives. I was seeing the kernel_task process and Opera reporting %1000+ CPU usage. I would only advise this if you need to, and if you are comfortable with the command line interface/BASH.
The tool is a diagnostic tool, so it doesn't seem to really serve much of a purpose outside of stress-testing your system and sending results to Apple. I was going absolutely insane from the system lag and found a blog mentioning this fix. Maybe the people with problems were deleting spindump completely or messing with file permissions. The fix creates a symbolic link with the "ln" command, so maybe that makes the system think the file hasn't been renamed. I am not really totally sure what the purpose of the "/usr/bin/true" file is (referencing the link below).
The blog page is here:
http://craigjolicoeur.com/blog/disable-spindump-on-os-x-to-prevent-system-slowdowns
Since macOS has SIP now, you need to temporarily disable SIP to make the change or just make the change in recovery. Since you have to boot into recovery to disable SIP, you might as well jut do it in recovery. If you are doing it in recovery, you don't need to use the sudo command and you will have to navigate out of the recovery partition and into the system partition. So I did this:
navigate to system partition:
cd /Volumes/Macintosh\ HD/usr/sbin
Check if you are in the right directory and see if spindump is listed:
ls
Rename spindump to spindump.disabled. You can still run the program manually by executing spindump.disabled:
mv spindump spindump.disabled
Create symbolic link:
ln -s /usr/bin/true /usr/sbin/spindump
That should do it. Then you can boot back into macOS. Keep in mind that after updates, you might have to repeat the process, as they will often create a new spindump file. Then you can do:
Delete old spindump:
rm spindump.disabled
Rename new spindump:
mv spindump spindump.disabled
I hope you are able to get your issue fixed one way or another.