While pretotyping has a marketing-ish side , I think its approach is interesting. Granted, it can be solved by other different testing approaches, but I think it has some merits to hold its own place. Also, despite the similar wording, I don't think it's the same as prototyping. Or at least, they have different intentions.
From Prototyping page:
Pretotyping differs from prototyping in one important respect. The
main objective of prototyping is to answer questions related to
building the product: Can we build it? Will it work as expected? How
cheaply can we build it? How fast can we make it? The main objective
of pretotyping is to answer questions about the product's appeal and
usage: Would people be interested in it? Will they use it as expected?
Will they continue to use it? ...
So, prototyping is more about creating some low fidelity version of a final product, but this low fidelity version is an attempt to create something as close as possible to the final product, reducing problems and focusing on the features the final product will have.
On the other hand, pretotyping looks to create as many different prototypes as possible, with features, visuals, tools and usability that you may NOT use, but looking for insight on what you can do and what you're missing.
Prototype is about trying to make a product's features to work.
Pretotype is about creating all the possible combinations of features that product may have, as crazy as they might be, and FAIL... or maybe not!
Take this with a sip of snake oil if you wish, but in the end, only time will tell if we will be pretotyping soon or just talk about it as just another gimmicky concept