While coming up with the best possible DR and HA plan for SharePoint is highly subjective and beyond the scope based on the information shared , I still have some really short and quick pointers for you.
Consider the 2 WFEs as "N" , you should think of using N + 1 architecture where you have a cold standby WFE (+1). Make them behind a Hardware based NLB, since Windows NLB supports not more than two systems per group and has the problem of sticky sessions.
From request balancing perspective its like in the event of complete failure N , your SharePoint does not become offline completly. Additionally, during server patching scenarios this topology would likely to help you with a least downtime upgrades incase you have groups of N+1 architecture working together.
Service Application Planning
While you havent mentioned what service applications will be used in the farm, SharePoint by design allows scaling on the basis service applications primarily. You need to plan for adding more servers to the farm, incase you wish to use service applications that are generally more resource hungry like Search, Excel and Word Automation services,etc. If you wish to configure your WFEs to act as Service application servers as well(which is not advisable), make sure you increase the current main memory by 2 times from the present and cpu cores to plus four.
If you just wish to use User Profile , BCS and Managed Metadata services probably these can be configured to run on both WFEs without the need of hardware upgrades as they relatively consume less memory and cpu.
Clustering SQL Server will give you redudancy, however if you are planning this for production you should consider using mirroring for Disaster Recovery site over SAN as well.Additionally, from performance and availability perspective think of separating Report Server from the primary host instance in the cluster if you are planning to use Reporting service over SharePoint Intergrated mode. Clustering SQL wont give redundancy on Reporting Services. So you may need
SQL Cluster + 1 Report Server(which will be also running SharePoint WFE role with reporting services addin as well)].