Unmanage port in VM Recovery Manager

A customer is hitting an issue that we have seen a few times with customers.

Discover / verify operation fails with the following error when issuing an inquiry command:
migmgr -f get_adapter -t vscsi -s U9080.M9S.21D5C47-V2-C418 -w 13857705842732564594 -W 13857705842732564595 -c RPA -a DR_COLLECT -U 6CB190F36A6B4512BABA8EBFA05F34AC -d 5
LU validation system call (START_TARGET_PORT) failed for storage target port with WWPN = 0x50050760444bce21.
Target Port being used for LU validation is busy. Reason : Migrating client partition is performing certain operations on the target port, interfering with LU validation process.
Failed to get the Fibre Channel devices information provisioned to the client partition, rc = 82

In this case, these have been identified as tape drives zoned on the HOME site "that occasionally get into an incorrect state on some VM's arbitrarily due to some events on the SAN". They are not needed at backup site.
Previous cases show this error is particularly problematic with tape devices, and are typically intermittent (making exact root cause difficult to debug). Cusotmers typically end up re-zoning them to avoid getting the discovery / verify operation failures.

We enquired about this with the development and were informed that:
"Currently user needs to remove tape devices from zones and KSYS managed VM's NPIV should not have access to these ports.
We have plans in the roadmap to support unmanage port, where customer can supply not required ports and VIOS can ignore them.
If port is unmanaged, it never be considered by VIOS and any disks from that port will also be ignored."

We are creating this RFE for this feature to be implemented.