We want all traffice destined for a public ip address to go in/out nic (10.1.1.20) and all public traffic to go in/out nic (173.x.x.x NIC)
I assume you meant "all traffic destined for a private IP address to go in/out NIC (10.1.1.20)" ?
If so, please could you provide a little more detail?
What private addresses do you have present in your LAN? Is it just 10.1.1.0/24? (i.e. 10.1.1.1 - 10.1.1.254) Or are there other private addresses (10.x.x.x; 172.[16-31].x.x; 192.168.x.x) to be concerned about?
Are you certain there are no public IP addresses in use on your LAN?
If you only need access to the 10.1.1.X network via your LAN NIC, then you should be able to do this by configuring your internet facing interface as the default. You can do this by lowering the metric of the default route configured on your internet facing NIC:
route CHANGE 0.0.0.0 mask 0.0.0.0 126.96.36.199 metric 10
EDIT: in response to your comments.
The 10.1.1.x addresses will already be routed via your LAN NIC, as they will be considered directly connected. See the third entry in your routing table:
Network Destination Netmask Gateway Interface Metric
10.1.1.0 255.255.255.0 10.1.1.20 10.1.1.20 20
In order to ensure the 10.1.2.X addresses will be routed via this interface, you will need another static route. The following command should work:
route -p ADD 10.1.2.0 MASK 255.255.255.0 10.1.1.1
The '-p' makes the route persistent across reboots.
Regarding my second question: there are some organisations that have both public and private address space within their internal networks (not on the internet). If you are certain that 10.1.1.x and 10.1.2.x are the only address ranges in use, then this does not apply.
Regarding two default gateways: this was previously not recommended as all default gateways would be installed with a metric of 1, which lead to ambiguity as to which route should be used for traffic matching the default route. In this case, your two default gateways have different metrics; the one with the lower metric will always be preferred as long as that interface is available. (See this answer for more detail).
Note that currently the default route via your 10.x.x.x interface has a lower metric (20, rather than 30), which will lead to any internet traffic being routed to your LAN.