abayer I've observed the following:

When running parallel steps with fastFail set, the fast-failed aborted build will return FAILURE if the act of aborting a step that was still in progress returns an error code. 

However if other parallel steps have finished successfully, and the last running step fails, this correctly returns ABORTED in the event of failure.

Some kind of race condition where if a step fails, fastFail aborts all other steps, and the last error code returned is the status seen by the declarative pipeline, but isn't the one respected by the overall build.status? Hopefully that makes sense. 

Is there not a reliable way to get from the rawBuild if a build was aborted?
I cannot image that there's no way - as the builds are eventually - when they are totally finished - always displayed with the right result. 'Only' currentBuild.currentResult is very often giving a different result (FAILURE usually)
We're using this hack now to get better detection of aborted builds:

if (currentBuild.rawBuild.getActions(jenkins.model.InterruptedBuildAction.class).isEmpty()) {
   return currentBuild.currentResult
} else {
  return "ABORTED"
}

Bulk closing resolved issues.

Thanks kutzi – this workaround is indeed very helpful! (Of course one would prefer a proper/clean solution/fix... )