I am attempting to rearchitect our MSSQL database such that we have two filegroups, one for data, on a 15K HDD, primary, and one for indexes on a separate SSD, indexes, in order to realize some performance gains (which I read could be debatable, but I think in my case it is true).

I would ideally like to create a table on primary with an index on indexes to realize these gains, however the PK constraint happens to contain the same columns we would normally query, therefore the clustered PK index must, by definition also live on primary.

Would I still realize any performance gains if I created a nonclustered index containing the same columns as the PK on the indexes FG?