Yes for the first two:

StrategyCode, HistoryDate

RRCode

3rd:

one index on TransactionAction, TrasactionEntityType,PrcessStatusFlag

Don't neglect the includes

The missing index views don't account for clustered index inheritance. Clustered index seek columns are appended to the end as seeks to every non-unique nonclustered index, and as includes to every unique nonclustered index.

SQL Server will never seek any further keys on and index beyond the one it has to seek on an inequality operation. So put all the equalities first, and then the inequalities. Preferabbly find the one most-used (unless some other queries seek it as an equality) and relegate the rest to includes since they'll never get used.