@C7NhtpnK Yes, because how Leap 16.0 is will be pretty much the same in Leap 16.N unless there is a compelling need for updating a package to a new version, for example a CVE that can’t be backported, or easier to release the updated version than try and backport fixes (I’ve done that in the past).
Remember Tumbleweed rolls forward and if toolchains change some things may no longer build for Leap 16.N in the development repositories, so those packages fall behind because they still build based on Leap releases.
Likewise package version numbers in Leap do not mean there are not security fixes when needed, many folks get caught out by that without checking changelogs and relying on scanners that only check version numbers.
You can see what is planned here: https://calendar.opensuse.org/ and updates in the Factory Mailing List for example;
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/X7QZT6ENSBW2JXVK4Y6ALFIYPBXEMWZ7/