Hi,
Based on my research, this issue has been addressed in Exchange 2016 CU12 and it is also included in the later CU.
So, I believe that the scanning tool needs to be updated or its better to check with the Nessus scan support forum.
If the above suggestion helps, please click on "Accept Answer" and upvote it