Index planning for many columns with different usage
If the only thing that inserts / updates data in this table is an out-of-hours process I'd be tempted to apply as many indexes as you can.  999 are allowed for a SQL Server 2012 table.  You can determine how many you need using the Database Tuning Advisor.

Obviously this will slow down the load process and consume a lot more disk space -  both from the indexes and the additional log data - but you can create a script to Disable the indexes prior to the load &amp; Enable them afterwards to speed things up.

If disabling indexes isn't available to you you can create a script to drop &amp; re-create them.