By all means, if all is well with the Sprint Planning and the team is unambiguous of what to build, it’s best to stick to Scrum and not pause for the DT deviation. Only in cases where the team struggles on the what to build, or needs a more deeper approach to determining it, this article throws the idea of using elements of DT for a breakthrough. As for prototyping and testing, my suggestion is to go back into the Sprint rhythm for the build part, so the designing and building of the prototype, and the testing and measuring would go into the Sprint Backlog. Hope this clarifies.