[exposure analysis] should change peer IsProtected definition?

[shireenf-ibm]

in following example : tests/exposure_test_with_anp_1/

$ ./bin/k8snetpolicy list --dirpath tests/exposure_test_with_anp_1/ --exposure
0.0.0.0-255.255.255.255 => hello-world/workload-b[Deployment] : All Connections
hello-world/workload-b[Deployment] => 0.0.0.0-255.255.255.255 : All Connections

Exposure Analysis Result:
Egress Exposure:
hello-world/workload-a[Deployment]      =>      [namespace with {conformance-house=slytherin}]/[all pods] : TCP 80
hello-world/workload-b[Deployment]      =>      0.0.0.0-255.255.255.255 : All Connections
hello-world/workload-b[Deployment]      =>      entire-cluster : All Connections

Ingress Exposure:
hello-world/workload-a[Deployment]      <=      [namespace with {conformance-house=slytherin}]/[all pods] : TCP 80
hello-world/workload-b[Deployment]      <=      0.0.0.0-255.255.255.255 : All Connections
hello-world/workload-b[Deployment]      <=      entire-cluster : All Connections

There is an AdminNetworkPolicy with subject a namespace hello-world and a NetworkPolicy selecting hello-world/workload-a
the connections defined in the AdminNetworkPolicy does not affect hello-world/workload-b
but still hello-world/workload-b is defined as protected by the policies, since it belongs to the ANP's subject group.
should we define it as not-protected when policies don't have affect on its exposure?