Right now the default wallet behavior unnecessarily leaks information about transaction creation times by using the next block height as the transaction lock height. This is not unlike the setting of nLockHeight for anti-fee-sniping, but at least that implementation introduces some randomness to increases the anonymity set.
Privacy and fungibility could be improved by either matching the lock height to the anti-fee-sniping height used, or to the maximum ref height of the inputs. In either case the change would be a bit more complex than this makes it sound as it would require adjusting the output amounts in a way that avoids truncation in round-trip conversion.
Right now the default wallet behavior unnecessarily leaks information about transaction creation times by using the next block height as the transaction lock height. This is not unlike the setting of nLockHeight for anti-fee-sniping, but at least that implementation introduces some randomness to increases the anonymity set.
Privacy and fungibility could be improved by either matching the lock height to the anti-fee-sniping height used, or to the maximum ref height of the inputs. In either case the change would be a bit more complex than this makes it sound as it would require adjusting the output amounts in a way that avoids truncation in round-trip conversion.