I don't know -- that should work (and works on other windows), but on Windows 8, I can't make it work on that console window at all. Works on the ConEmu window, can I convince you to upgrade your console?
http://code.google.com/p/conemu-maximus5/

My first computer is installed with Windows 7 and Powershell v3 and your Wasp2 works fine.
But with another with Windows 7 and Powershell V2 it doesn't work.
The two first import-module work fine.
But the third failed.

Import-Module \PBCApplic\Applic\Outils\Scripts\PowerShell\WASP\WASP.psm1
Unable to find type [System.Windows.Automation.ControlType]: make sure that the assembly containing this type is loaded
.
At \PBCApplic\Applic\Outils\Scripts\PowerShell\WASP\WASP.psm1:427 char:57

That class is in uiautomationtypes, which is explicitly loaded by the module, so I'm not sure how it could fail. Run the add-type line by hand and then test that you can access that type by just writing [System.Windows.Automation.ControlType] in the console.

The only thing I can think of is that you're having a problem loading assemblies because it's on a UNC share (they changed the security model around that in .net 4, which PowerShell 3 uses automatically), so you could try making a local copy on the box, if
the test above succeeds.

I'm just a user (recently advanced ! but not ultra advanced !!) of powershell.
Your links are for "Autoload Module 1.2.ps1", "Reflection Module 4.1.ps1" and "UIAutomation 1.9.ps1"
I rename thee files like "Autoload.psm1", "Reflection.psm1" and "WASP.psm1"
I unblocked them.
And in a powershell (V2) console, I strike :
Import-Module C:\Temp\Autoload.psm1
Import-Module C:\Temp\Reflection.psm1
Import-Module C:\Temp\WASP.psm1
I got no message with the two frst commands and an error with the third.
If I strike the line Add-Type -AssemblyName "UIAutomationTypes, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" I can then re-execute the third line without errors ...

It seems like you're on PowerShell v2, so unless you've tweaked PowerShell.exe.config, your host will return $PSVersionTable.CLRVersion as something like 2.0 -- which will result in running that Add-Type line in the module. If you want, you could tweak the
WASP.psm1 module to remove the 4.0 stuff, but just remember you did that in case you upgrade to PowerShell 3 later:

I add a line in the WASP.psm1 just before the first IF : Write-Host "Hello"
With py powershell v2, after importing module Autoload and Reflexion, when I want to import the wasp module I get the error.
If I add the type manualy and re-import the wasp module I get my message "Hello".
It seems like the import-module pre-compile the file before executing it.