I recently ran into a situation where I discovered half of our recently spun-up AD servers did not have a SYSVOL or NETLOGON share. This happens for a variety of reasons, almost all of them when the DC is promoted. That being said, hardly anyone ever thinks to check for their existence. This would basically make it easier to identify a promotion problem before it becomes a headache for the helpdesk.
I have already implemented this by modifying the default template to include 2 PowerShell scripts for "Share: NETLOGON" and "SHARE: SYSVOL" with simple PowerShell scripts running on the remote host:
$path = "\\" + $env:COMPUTERNAME + "\NETLOGON\"
$result = [int](Test-Path $path)
Write-Host "Message: " $path
Write-Host "Statistic: " $result
Exit 0;
For SYSVOL, I change NETLOGON to SYSVOL. There's no reason why it couldn't be "Critical Shares" and be a single roll up, this is just the way I did it.