Not quite, latency will increase as you increase sample size, but latency will decrease if you up the sample rate (note different terms here, ‘size’ vs ‘rate’). Sample size we understand to mean the 32,64,128 etc number, sample rate is the kHz number (44.1kHz, 192kHz etc). There’s plenty about those online that you can read to explain what they are.
Essentially, a sample rate of 192kHz (which very very few people work at tbh) will allow for a lower latency than 44.1kHz. But higher sample rates require more CPU power. An overworked CPU might cause clicking audio, which means you might then choose to sacrifice low latency (by upping your sample size) to clear up the audio. Lowering your sample-rate to say 48kHz would increase your latency, but would require less CPU resource, thus allowing you to reduce your sample size to decrease latency.
If that all sounds ‘swings and roundabouts’ that’s because ultimately it is. It’s very much a balancing act between what sample rate you want/need to work at, the power of your computer (CPU speed, memory, hard drive capacity), and how much latency you can bear to work with whilst recording. Latency can be completely negated by monitoring your input signal directly from the interface (if that feature is present), however that would mean not hearing any applied plugins to that track whilst recording real-time (of course, you'd hear it upon playback of your recording).
Aside from that, can’t really comment too much on the interface, i’m somewhat biased
Si