You'd like a failure anywhere in the load to cause the destination DB to be marked suspect and need to be restored from backup? That's what you're asking when you ask for unlogged operations (which don't exist)

You can change the batch size, you can see if it's possible to get the SSIS to run BULK INSERT or similar, which can be minimally logged, but SQL does not run any unlogged operations because if it did, a single error (pk violation, fk violation, data type mismatch, etc) would result in a suspect DB because it would have no way to roll back part of the operation.