The bike speed cadence profile calls the timestamp the "Bike Cadence Event Time". However, there's no specification what that event is, e.g. the p.o.t. when the magnet passes the sensor. So a developer may freely implement whatever s/he likes, either use an event driven approach, sampling, ...
To make it short: the device profile doesn't really specify what you would need.