nickspeed,
I think the consequences of files being ruined would be minimal (affecting one to a few files when in use during a scan). In fact after doing some research after my posting, it's been told that interrupting chkdsk would not make a volume more corrupt than what it was before. So if you feel that if you have any time to spare in the future, you can run chkdsk to continue fixing those corruptions from when you interrupted it.
One intuitive step to make sure that chkdsk isn't using the hard drive/solid state drive is to take note of the percentage or what it's currently doing. If it hasn't advanced since then, I would gather it's not doing anything and you can safely shut it down.
Hope that clears it up.
Source: https://docs.microsoft.com/en-us/previous-versi...(v=ws.11)