ProximityLockDetection logic changes
The first one, I think, is the most important because it changes the main function of the app, the actual proximity detection logic (in a good way). But by default, these options are turned off, and everything works the same as before until you enable them.
“Request more signal readings” changes the way macOS reports the monitored device signal readings. When enabled, it asks macOS's Bluetooth stack to report each broadcast it receives instead of combining reports, and it may help detect device movement a bit quicker.
“Filter burst readings” is a bit more interesting. It is basically doing reading deduplication at the application level, but in a slightly different way than macOS does. This can reduce signal fluctuations, so you will see fewer strange fluctuations where the signal goes below the threshold when it should not (for example, when your iPhone or Watch hasn't been moved away).
In my own testing, enabling both options changes the Kalman filter behavior positively and noticeably. I can't, however, guarantee that it will work the same exact way for your setup as it does for my testing devices. But it's worth trying them anyway, either both together or each one separately.
Geofencing
The second feature, which might also be very useful, is geofencing based on the connected Wi-Fi network name. You can now pause ProximityLock's actions on selected Wi-Fi networks, or the other way around, allow actions only on those networks. It needs Location permission, even though it only needs to read the Wi-Fi network name, but that's how the macOS permission system works.
Screen wake up
The third one, “Wake the screen on return”. Well, it just wakes your screen when you return to your Mac if enabled.
Lock screen status
The fourth feature: a lock screen status widget, which shows the current signal level and device status. I think it's nice to see sometimes what is happening with ProximityLock even if the screen is locked.
Return shortcut timing
Last one: separate return shortcut timing. Previously, both return and away shortcut actions waited for the same amount of time you set on the main screen using the away delay slider. But now return shortcuts will no longer wait for the Action delay by default. If you prefer the previous behaviour, you need to enable “Wait the action delay before running” in the shortcut settings modal (inside ProximityLock app).
One more thing: I added a change that should help prevent macOS from killing ProximityLock during high memory pressure cleanup. It tells macOS that proximity monitoring is important work that should keep running.