The problem is not LBS, the problem is inside PBS (physical block size) and the features allowed by manufacturer.
Basically are two kinds of formats, one is e.g. “nvme0” which format the PBS and one is e.g. “nvme0n1” that correspond to LBS.
Some manufacturers allow to instruct the controller (nvme0) to use another format (e.g. 4096 PBS) and some others don’t.
The same is for LBS, some allow to switch between 512 and 4096 (nvme0n1) and some others don’t (like Sa*****).
Basically, Win need a PBS or at least a LBS of 512, all other OSs doing very well with 4k, many applications under Win don’t do well with 4k neither in PBS nor LBS. So, manufactures want to stay compatible with Win use 512 and others give the possibility (at least) to switch to 4k.
The bad thing is, even if all specified performance are given for 4k, none manufacturer tell clear in the data-sheet which kind of PBS is used by the controller.
The worse is, some manufacturers deliver first NVMe with 4k PBS and later on with 512.
Transparency & support is totally different to what we experience and this with all manufacturer.
The PBS and LBS must be specified, and the controller must be opened to modify PBS and LBS, that’s all.
At least, if PBS is 4k you get better performance with 4k LBS, and if PBS is 512 you get better with 512 LBS because of not misalignment of blocks.