I'm thinking no. The the primary database needs to be in FORCE LOGGING mode. Database trumps table.
The Gains and Pains of Nologging Operations in a Data Guard Environment (Doc ID 290161.1)
Compress is not an issue.
You might consider a logical standby for ETL work.
Technically there is nothing preventing you from NOT setting FORCE_LOGGING=TRUE and then using NOLOGGING operations.
However, the blocks would be marked as "logically corrupt". Any subsequent non-direct path DML against those blocks may fail to execute on the Standby and would halt replication of redo.
So you would use NOLOGGING operations only against tables with *only* operations like Direct Path INSERT and TRUNCATE and no other normal DML.
Of course, when you open the Standby it becomes your job to identify which operations have not been applied to this table and manually apply them (run ETL for example).
Never tested this. It might or might not work !
Hemant K Chitale