There are no special considerations for replication of last Logontime Stamp.If the attribute is updated it is replicated like any other attribute update.
Logon types and that will trigger an update to the last Logontime Stamp attribute.The last Logontime Stamp attribute is not updated with all logon types or at every logon. In Windows Server 2003 we introduced the last Logontime Stamp attribute.Administrators can use the last Logontime Stamp attribute to determine if a user or computer account has recently logged onto the domain.It is an attribute of the domain NC and controls the granularity (in days) with which the last Logontime Stamp attribute is updated. Meaning that if you look at this attribute in ADSIEDIT. This just means the system is using the default value of 14.
The last Logontime Stamp attribute is not updated every time a user or computer logs on to the domain.
Note: If the ms DS-Logon Time Sync Interval is less than 5 days, the randomization is not put into effect. If you want to disable the last Logontime Stamp feature set the ms DS-Logon Time Sync Interval attribute to 0.
I personally have never spoken with anyone that really had a business need to change how often last Logontime Stamp needs to be updated.
The last Logon attribute is not designed to provide real time logon information.
With default settings in place the last Logontime Stamp will be 9-14 days behind the current date.
If you need a different time interval you will need to adjust the value of the ms DS-Logon Time Sync Interval attribute to a value between 5-100,000. (I guess the dev was counting on medical science to solve that pesky aging problem.) In my experience the default settings can accommodate almost anyone and there is no need to change the update interval.