Although the idea sounds good in principal (and is something we have thought about), I think that in practice it would not prove that useful.
Even on small maps with a high data density it is uncommon to get data points in exactly the same position, so to get any sort of reasonable number of cross-matched data points you would need to define some sort of distance over which you assume that the depth doesn't vary (say, a 5m radius) - but of course the depth will vary across some of those areas, perhaps by more than the tidal influence. Then, as Trevor mentioned, you also need to consider the accuracy of your GPS position, and indeed the accuracy of your depth readings. Even given all this, I still think it is unlikely that you would get a sufficient number of usable data points in a single short track and the number of potential inaccuracies along the way could lead to wildly inaccurate results by the end. Perhaps if you combined this with outlier elimination and some sort of curve fitting to the known tide shape.. but I think it would be a lot of effort to get enough data points to make it work. In any case, if you know the tide for the area it is probably far easier to simply enter a few known times/depths and let RM interpolate the rest.
Having said all that, if you do want to try this then it is easy to import your own tides into RM. Just create a CSV file containing UTC time and the depth offset and import into a new tidestation. Values between supplied points will be calculated using a straight linear interpolation, anything outside of the beginning or end of the supplied times will take the offset of the first or last value.