I would suggest that you raise this as a separate issue, outline the problem you have, and ideally suggest a way of fixing it.
If you can identify a way whereby the plugin can poll to see if there are new changes more efficiently then that news would be welcomed.
Ideally, if you register on GitHub, fork the jenkinsci-accurev plugin code, work on an update, push your changes onto github, and then do a "pull request", you stand a very good chance of having your changes accepted (and even if you don't, you can build your own plugin using Jenkins).
Basically, AccurevSCM.java does nearly everything, and its pollChanges(...) method gets asked if it should do a new build or not.
At present, that code uses the same algorithm that's used to determine what the changes are to determine if there are changes. If you can find a better method, say so (but in a new issue) - all we need to do is answer the question "Given that the last build happened at <datetime>, do we need to do another build now?", but we need to be able to answer that question without a workspace.
If you know of an accurev command (or series of commands) that'll do that (in an efficient manner), please raise an enhancement request saying what it should do instead (however, as far as I am aware, accurev's client API isn't capable of doing this in an efficient or reliable fashion).