After analyzing several reports, here are the possible causes that may trigger this problem:
If you are using a third-party firewall and it is conflicting with Windows Firewall, this issue can be caused.
In case you have set up too many rules in Windows Firewall, it can result in excessive CPU usage of LocalserviceNoNetworkFirewall. You can try deleting custom firewall rules in that case.
This issue can be caused if you are dealing with the corrupted installation of your third-party firewall program and it is conflicting with Windows Firewall. In that case, uninstalling and then reinstalling the third-party firewall might help you fix the issue.
Another reason for this problem can be corrupted customizations or settings of the Windows Firewall. If the scenario is applicable, you can set the Windows Firewall to default configuration to resolve the problem.