Yes, the idea behind the first is/was to help people making an action (proper command line) interactively (of course it is just a sketch).
If you prefer is - or is intended to become - a way to prevent people from using incorrect syntax and attempt to "guide" them to make a proper command.
The only "good" thing it adds is the piping to "more" so that the help screen doesn't scroll away (this could be a "native" addition to the actual .exe), I know from experience how most "common" users will have difficulties with this, which is typically what the Author and "power users" know how to deal with, but rest assured, rarely the "average user".
The idea behind the second is something else.
I use a known Linux example to explain this.
Say 95% of people using Linux never used tar if not to UNtar something.
I.e. the command line tar -xvf <something> is used in a ratio of approximately 12747:1
It makes a lot of sense to make an alias "untar" to "tar -xvf".
The common action a normal user may want to do to a .wIm file regarding "info" could be to make one image bootable and know the names/description of the images inside it (most of the other info is useful, but not "commonly needed").
Another thing that may have some use (though right now I have no idea of what it could be) is the GUID.
IMHO noone normally would want to know:
- Compression type
- Part Number
- Integrity info
- Relative path junction
- Directory count
- File count
- Total Bytes
- Hard Link bytes
- Creation time
- Last modification times