Does composite cluster index affect performance of seek/scan non-cluster index which is part of the composite?
First off, don't mix "primary key" and "clustered index". One is "how to identify a row", the other is "on-disk structure"

Then, you don't need an index on Division by itself because it is the left hand column of the clustered index. However, it won't be covering (see links below)

And for each point in turn:


this table doesn't know that "Brcode is unique for all division". If it is, then brCode should be first and unique and the clustered index by itself
a search on TrDate won't benefit from the clustered index
it depends on selectivity, statistics, how many columns are required. It may seek with a key lookup or it may scan the clustered index (= a table scan) or scan/seek the index on TrDate


Finally, I'd suggest some background reading:


SQL Server Index Basics
Using Covering Indexes to Improve Query Performance