Hi,
As far as I am concerned, with one NIC on each node, the cluster can be setup, and in some degree, we can't say it is single point failure, since the cluster is already work as high availability.
Assume that the NIC on one Cluster node is failed, then the heartbeat to that node will be failed, and then that node will be removed from the Cluster membership, at that time, roles on that node will failover to other possible nodes. The roles in the Cluster will not affect.
However, if the (virtual) switch has issues, cause the hold cluster has a network connection issue, then, the cluster will be down.
Although one NIC on each node is supported to create the SQL cluster, it's highly recommended to add an additional network for the heartbeat, as described above, heartbeat packet is lightweight and important, for SQL services, if there's heavy network traffic, the heartbeat packets will lose, so it's recommended to create an additional heartbeat network to make the cluster more stable.
Thanks for your time!
If the reply could be of help, please help to accept it as an answer, thanks for your cooperation!
Thanks for your time!
Best Regards,
Anne